Telecoms for agents & MCP

Begin with discovery

An agent can help turn a business brief into search criteria: category, area, pattern and intended use. The public read-only endpoint below searches the observed Switch 03 catalogue and returns its source and check time. It does not query private accounts or reserve a number. Provider confirmation is still required for price and availability.

Distinguish reading from acting

Number-type information and provider searches are read operations. Reserving, buying, porting, changing routing and placing calls have consequences. They need verified account authority, narrow permissions and approval attached to the specific proposed action.

Connect to the public number tools

Endpoint: https://ins-net.co.uk/mcp.php. Send JSON-RPC 2.0 requests using HTTP POST and Content-Type: application/json. The endpoint supports MCP protocol version 2025-06-18, with initialize, ping, tools/list and tools/call.

This public service has no authentication because it exposes only public catalogue listings and number-category explanations. Do not send private information, account details or credentials.

search_public_numbersSearch the observed public Switch 03 range. Optional digits: up to 11 digits. Optional tier: all, Standard, Silver, Gold or Platinum.describe_number_typeExplain a category. Required category: local, national or freephone. It does not identify a current carrier or check availability.

List the available tools

After initialising an MCP session with the supported protocol version, send this JSON body:

{"jsonrpc":"2.0",
"id":2,
"method":"tools/list",
"params":{}}

The response describes the two read-only tools and their input schemas. A listing is not a reservation, quote or entitlement to use a number. Provider catalogue errors are reported rather than replaced with invented availability.

A public search example

{"jsonrpc":"2.0",
"id":3,
"method":"tools/call",
"params":{
"name":"search_public_numbers",
"arguments":{
"digits":"077",
"tier":"Standard"}}}

This reads public catalogue data only. It cannot reserve, purchase, port, alter routing, place calls or access private Switch accounts.

Future authenticated action tools

The following action names illustrate a future authenticated integration. They are not callable tools on this website and do not claim an operational Switch provisioning API.

quotes.preparePrepare a reviewable offer request without purchasing or reserving.routing.proposeDescribe a change and its effect; do not apply it.changes.submit_approvedAccept a specific approval, validate scope, then use an authorised provider connector.

Provider access, authentication, integration and testing are prerequisites. Every write needs an outcome check and a recovery path; a timeout is not proof that an action failed.

Use MCP with the right boundaries

MCP lets servers describe tools and their input schemas for clients to discover and invoke. A tool description is not authorisation. The application still needs identity, scoped access, input validation, visible actions and a human ability to approve or deny consequential operations.

Read the MCP tools specification ↗

Design a useful first pilot

Start with number research or quote preparation. Test stale availability, missing account authority, changed prices, tool errors and declined approval. Review source accuracy and the final business outcome before extending the integration to provisioning or calls.

Discuss an agent telecoms project ↗

Tools that connect.Permissions that mean it.