Agoragentic

agoragentic_call_service

Invoke a stable x402 service by slug. Send an initial call to obtain a payment request, then retry with a payment signature to complete the transaction.

Instructions

Call one stable x402 service by slug. The first unpaid attempt returns an x402 Payment Required payload. Retry the same tool call with payment_signature to complete the paid call.

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": {
      "slug": "<slug>"
    },
    "name": "agoragentic_call_service"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	Stable x402 service slug, for example text-summarizer.
`payload`	No	JSON payload sent to the stable edge route.
`max_price_usdc`	No	Optional safety bound. The tool errors if the quoted service exceeds this price.
`payment_signature`	No	Optional PAYMENT-SIGNATURE value used on the paid retry.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.2May 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only indicate readOnlyHint false, openWorldHint true, etc., but the description discloses the critical payment behavior: an unpaid attempt yields a Payment Required payload, and a retry with payment_signature completes the call. It does not cover failure modes beyond payment but sufficiently reveals the tool's non-read-only, payment-gated nature.

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?

Two sentences with minimal redundancy. The first sentence states the core purpose, and the second explains the retry mechanism. Every word earns its place; no filler.

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?

The tool has a non-trivial payment flow, and the description explains the two-step invocation pattern clearly. It also notes the first response type (Payload Required) and the retry condition. While no output schema exists, the description conveys enough context for an agent to invoke it correctly. It could mention the final success response, but the phrase 'complete the paid call' implies the service result.

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 input schema already describes all four parameters, so the baseline is 3. The description clarifies that payment_signature is only for the paid retry, matching the schema's 'used on the paid retry.' It does not add extra meaning beyond the schema's descriptions, but the high coverage means no deduction.

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?

The description opens with 'Call one stable x402 service by slug,' a specific verb and resource that clearly identifies the tool's action. It distinguishes from siblings like quote/browse by focusing on execution and the payment retry flow. The title 'Call x402 Service' reinforces this purpose.

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?

The description provides clear guidance on the two-step payment flow: first unpaid attempt returns Payment Required, then retry with payment_signature. However, it does not explicitly compare to sibling tools or state when to choose this over quote_service/browse_services, though the 'call' vs 'quote' distinction is implicit.

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