Sparetext

Ask the user to buy a business number

request_business_number

Idempotent

Get the user a link to buy a business number you found with search_numbers. Nothing is bought and no money moves: the link opens the Business number tab in their Sparetext dashboard with this number ready, and they press Buy ($4 held from their balance). Give the user the link. Asking again changes nothing.

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": {
      "number": "<number>"
    },
    "name": "request_business_number"
  }
}

Input Schema

Name	Required	Description	Default
`number`	Yes	A toll-free number from search_numbers, like +18335550100

Output Schema

Name	Required	Description	Default
`url`	Yes
`number`	Yes
`needsOwner`	Yes
`balanceCents`	Yes
`monthlyCents`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing that nothing is bought, no money moves, the link opens the Business number tab in the Sparetext dashboard, and the $4 hold only happens when the user presses Buy. It also reinforces the idempotentHint with 'Asking again changes nothing,' which tells the agent not to retry for a different outcome.

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

Conciseness4/5

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

The key fact (it's only a link, no purchase) is front-loaded in sentence two. A couple of short imperatives ('Give the user the link', 'Asking again changes nothing') repeat points already made, costing a little tightness but adding emphasis rather than noise.

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

Completeness4/5

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

For a one-parameter hand-off tool with an output schema and full annotations, the description covers the essentials: what it returns (a link), what it costs (nothing until Buy), and idempotence. It does not say what happens for an invalid or already-owned number, a minor gap given the simplicity.

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 the schema already documents the single 'number' parameter with a format example, so the baseline is 3. The description adds a small amount of meaning by emphasizing the provenance constraint (a number found via search_numbers), which slightly exceeds the schema text.

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 ('Get the user a link to buy a business number') and ties it to the sibling that produces the input ('you found with search_numbers'). An agent can distinguish this from search_numbers or submit_number_verification without opening any 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?

Clear precondition: the number must come from search_numbers, and the description makes explicit this is the hand-off step rather than the purchase. It doesn't name a competing alternative or state when not to call it, so it falls just short of full routing guidance.

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

All Sparetext 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?