Check live readiness, x402 network and prices before spending. This free call has no side effects.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states the call is free and has no side effects, which is critical safety information for an agent deciding whether to invoke it.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one concise sentence that front-loads the tool's purpose and ends with the key safety caveat. Every word earns its place with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read-only status tool, the description covers purpose, timing, and side-effect profile. Since an output schema exists, omitting return-value details is acceptable, and the description gives an agent enough to invoke the tool appropriately.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so there are no parameter semantics to document. The description appropriately avoids inventing parameter details, and the baseline for a parameterless tool is strong.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Check') and a clear resource: live readiness, x402 network, and prices. It signals the tool is a pre-payment status check, which helps distinguish it from payment-executing siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'before spending' gives clear contextual guidance on when to use the tool. It does not explicitly name alternatives or exclusion cases, but the timing is unambiguous for an agent deciding whether to call it first.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The four get_*_ayment tools all create live x402 challenges and differ only by product, while get_quote and get_example_payment both provide example input data — creating real selection ambiguity. Descriptions do clarify the product and side-effect differences, but an agent must read carefully to avoid picking the wrong one.
All tools use lowercase snake_case with a verb prefix, and the get_X_payment pattern for challenge creation is consistent. However, 'get' is overloaded to cover both free reads that create no side effects and challenge creation calls, and get_payment_preflight_payment has a redundant 'ayment' that muddies the naming pattern.
Eight tools map cleanly to the paid-evidence workflow: status check, quote, four product-specific challenge creators, payment submission, and a capability-request escape hatch. Each tool earns its place, and the count is well-scoped for a niche paid API.
The core quote→challenge→submit→result flow is covered, and request_capability is a good gap-filler for missing products. Minor gaps remain: there is no explicit result-retrieval tool beyond request_id replay, and product discovery is implicit through get_quote and get_service_status rather than a dedicated list endpoint.
