Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

paytocall_info

Explains the Pay-to-Call payment rail for AI agent phone calls, including per-call USDC pricing on Base and paying before a phone number is revealed.

Instructions

Describe the Pay-to-Call rail at x402-agent-pay.com — the payment rail for AI agent phone calls. AI caller bots now dial businesses on their own; Pay-to-Call lets a business set a per-call price in USDC on Base, and the phone number is only revealed to an agent after it pays. Returns live routes and the flow.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "paytocall_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description must carry the behavioral burden; it does signal that this is a read-only informational tool ('Describe', 'Returns live routes') and explains the underlying payment flow (per-call USDC price on Base, number revealed after payment). It says nothing about auth, rate limits, freshness/caching of the 'live' data, or response shape.

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?

Three tight sentences with the domain URL front-loaded and the mechanism explained compactly. The middle sentence is useful context rather than filler. Slightly verbose in the setup ('AI caller bots now dial businesses on their own') but not wasteful enough to penalize heavily.

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

Completeness3/5

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

There is no output schema, so the description should clarify what is actually returned; 'live routes and the flow' is vague and leaves the agent unsure of the payload's form or usefulness. For a no-parameter info tool this is roughly adequate, but the return-value ambiguity and the unaddressed overlap with pay_to_call_info keep it at minimum-viable.

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?

The tool takes zero parameters, so there is no parameter semantics to convey and the empty schema is self-explanatory. Baseline 4 applies; nothing in the description is needed or missing here.

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

Purpose4/5

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

The description names a specific resource (the Pay-to-Call rail at x402-agent-pay.com) and states what the tool does: describe the rail and return live routes plus the flow. It is more than a restatement of the name. However, it does not distinguish itself from the near-identically named sibling pay_to_call_info or from settlement_rail_info, leaving real ambiguity about which info tool to pick.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The phrase 'Returns live routes and the flow' only weakly implies this is a discovery/read tool. Given a sibling literally called pay_to_call_info, the absence of any routing guidance is a meaningful gap.

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

Deploy Server

Other Tools