Conecto

Rent a phone number

phone_rent_number

Rent a number found by phone_search_numbers. It is the business's at once; callers reach the AI assistant after phone_setup_assistant has run. This call pays the first month; it then renews monthly from the balance (if the balance is short there are 7 days' grace, then the number is released). Up to 5 numbers per account. Costs the price in the quote (at most $25.00); nothing if it fails.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "quote": "<quote>"
    },
    "name": "phone_rent_number"
  }
}

Input Schema

Name	Required	Description	Default
`quote`	Yes	The quote of the number to rent, from phone_search_numbers.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond annotations (readOnlyHint=false, destructiveHint=false): discloses first-month payment, monthly renewal from balance, 7-day grace before release, a 5-number-per-account cap, cost ceiling of $25.00, and 'nothing if it fails.' This is rich behavioral disclosure an agent could not infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four dense sentences, front-loaded with the action and prerequisite, followed by cost/billing and limits. No filler; every clause carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter mutation tool with no output schema, the description covers cost, renewal, grace period, caps, and failure behavior—everything needed to call it confidently and understand the financial consequence.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents 'quote,' so baseline is met. The description adds meaning by tying the quote to phone_search_numbers and stating the price bound ('at most $25.00'), plus the failure-refund behavior, giving extra semantics about what quote represents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Rent a number') and immediately ties it to the sibling that produces its input ('found by phone_search_numbers'). An agent can distinguish it from phone_search_numbers, phone_release_number, and phone_list_numbers without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly establishes the prerequisite ('found by phone_search_numbers') and the related setup step ('callers reach the AI assistant after phone_setup_assistant has run'). It doesn't spell out when not to rent, but the dependency chain gives clear usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Conecto tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?