Skip to main content
Glama

aqb_x402_call

Call an AQB x402 endpoint: GET, read the 402 terms, pay AQB, retry with X-AQB-Tx, return the resource

Instructions

Call an AQB x402 endpoint: GET, read the 402 terms, pay AQB, retry with X-AQB-Tx, return the resource

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": {
      "url": "<url>"
    },
    "name": "aqb_x402_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
bodyNo
methodNo
accountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.6

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key multi-step behavior: GET, read 402 terms, pay AQB, retry with X-AQB-Tx, return the resource. It does not disclose payment cost, authorization or balance requirements, failure handling, or idempotency, which are important for a payment-related tool.

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?

The definition is one tightly packed sentence that front-loads the action and then summarizes the flow step by step. There is no wasted wording, and the sequence is easy to scan.

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?

For a complex payment-flow tool with no annotations, no output schema, and undocumented parameters, the description gives a useful outline of the 402 handshake. It is still incomplete regarding parameter meaning, authentication context, and error or failure behavior, so an agent would need to inspect the schema and infer several details.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for all four parameters. It does not explain what 'account' means, how 'body' is used, or when to use POST versus the mentioned GET; the mention of GET may even confuse the method enum that includes both GET and POST.

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 states a specific verb and resource: calling an AQB x402 endpoint. It also outlines the retry flow, so an agent can understand the tool's core purpose without opening the schema. It does not explicitly differentiate itself from siblings such as aqb_pay or aqb_quote.

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

Usage Guidelines3/5

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

The phrase 'Call an AQB x402 endpoint' implies the usage context: endpoints that return HTTP 402 terms. However, it gives no explicit guidance on when to choose this tool over aqb_pay, aqb_quote, or other sibling payment tools, and it lists no exclusions or prerequisites.

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