Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

settlement_assurance_info

Retrieve opt-in settlement-failure insurance terms for x402 resource providers, including premium, claim window, and verified payout limits.

Instructions

[FREE] Settlement Assurance from the AgentPay x402 facilitator: opt-in settlement-failure insurance for x402 resource providers. Terms (live from the pool endpoint): 0.1% premium per settled amount charged to the enrolled resource, claims for facilitator-side settle failures filed within 72 hours, verified claims pay up to 25 USDC on Base from the shared pool. Enroll: POST https://x402-agent-pay.com/facilitator/insurance/enroll with {resource, wallet, contact}. Claim: POST .../insurance/claim with the settlement receipt and failure proof. Human page: https://x402-agent-pay.com/assurance/ Pass

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

Input Schema

NameRequiredDescriptionDefault
resourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/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 full behavioral burden; it does disclose that access is free, that terms are live from the pool endpoint, the 0.1% premium, the 72-hour claim window, and the 25 USDC Base payout cap. However, it never says whether calling this tool is a read-only lookup or performs an action, and the inline 'Enroll: POST ...' / 'Claim: POST ...' text risks being read as effects of this tool rather than separate HTTP steps.

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

Conciseness3/5

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

The '[FREE]' flag and the headline sentence are well front-loaded, but the paragraph mixes product terms, HTTP endpoints, and a human URL without clear separation. It also ends with a dangling fragment ('Pass ') indicating truncated content, which wastes space and signals incompleteness.

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 no-output-schema info tool, the description does convey the substance an agent would want (premium, claim window, payout cap, how to enroll/claim), which is more than many peers provide. It still omits what the response actually contains and what the 'resource' parameter filters, and the truncation leaves an unresolved clause.

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 coverage is 0% for the single optional 'resource' parameter, so the description is the only possible source of meaning and it never explains what the parameter does or how it scopes the terms returned. 'resource' appears only in the enrollment body description, not as a tool parameter, which could actively mislead.

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 identifies the offering (opt-in settlement-failure insurance for x402 resource providers from the AgentPay x402 facilitator) but spends most of its words on product policy rather than on what this specific tool call returns. The 'info' suffix and 'Terms (live from the pool endpoint)' phrase imply a read of current terms, yet that is never stated outright. It also does not distinguish itself from nearby siblings such as settlement_rail_info or facilitator_policy_info.

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?

Enrollment and claim endpoints with payload shapes are given, which is useful follow-on guidance, but there is no statement of when an agent should call this tool versus the many related settlement/facilitator info tools. The implicit usage (read terms before enrolling or filing a claim) is left for the agent to infer.

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