Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pay_to_call_info

Initiates a pay-per-call session to a registered business and returns the phone number after USDC payment settles.

Instructions

[FREE] Pay-to-Call: the x402 payment rail for AI agent phone calls. Businesses register a phone line + per-call USDC price and earn USDC on every agent call (auto-disbursed to their wallet, 1% rail fee). Agents pay per call in USDC on Base L2; the phone number is revealed only after payment settles. We move the money, not the voice — bring your own telephony (Bland, Twilio, anything). GET https://x402-agent-pay.com/pay-to-call/api/businesses — public directory POST https://x402-agent-pay.com/pay-to-call/api/call/start {"business": ""} — x402 gated, returns session + phone number POST ht

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": "pay_to_call_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
businessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose useful traits: the 1% rail fee, USDC settlement on Base L2, phone number revealed only after payment settles, and the [FREE] marker. However, it never says whether invoking this tool incurs payment or performs a call, and it is truncated mid-sentence ('POST ht'), leaving the flow incomplete.

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

Conciseness2/5

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

The text is a promotional blurb wrapped around raw HTTP endpoint listings rather than tool-oriented guidance, and it cuts off mid-URL. The most relevant information for an agent caller is buried rather than front-loaded.

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

Completeness2/5

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

No output schema and no annotations mean the description should explain what the tool returns and its cost profile; it does neither, and the truncation leaves the documented API flow incomplete. For an info tool in a crowded sibling namespace this is insufficient.

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

Parameters3/5

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

The single 'business' parameter has 0% schema coverage, but the description's example payload {"business": "<slug>"} and the reference to a public business directory do convey that it is a business slug. That is partial compensation for an otherwise undocumented parameter.

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

Purpose3/5

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

The description explains the Pay-to-Call service (register a line, set a USDC price, agents pay per call) but never clearly states what this MCP tool itself does — presumably return info/docs — versus the raw HTTP endpoints it lists. It also gives no differentiation from the near-identical sibling paytocall_info.

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 when-to-use guidance, no prerequisites, and no mention of alternatives — notably it does not route the agent away from or toward the sibling paytocall_info. An agent must infer from the name alone that this is an informational tool.

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