Skip to main content
Glama

Underwrite pools

underwrite_pools
Read-onlyIdempotent

Free sample: https://apexfaucet.xyz/arc/underwrite/ ($0.003). Agent-bond pools as the page lists them. Does not deposit, cover or slash. Not advice. $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The description contributes real behavior beyond annotations: pricing ($0.003/call), accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the non-mutating scope ('Does not deposit, cover or slash', 'Not advice'). That said, there is tension with readOnlyHint=true — paying for a call inside the tool is a financial transaction, and the description never clarifies whether funds move or how a failed payment is handled.

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?

Front-loaded with a promotional 'Free sample' link, and the price '$0.003' is stated twice in five short sentences. The critical instruction (call without payment first) sits at the end rather than the beginning, working against front-loading.

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?

With no output schema, the description carries the burden of describing what a call returns, yet it only says 'as the page lists them' and refers the agent to an external URL. Given a one-optional-parameter tool this is not catastrophic, but the response shape is unknown to the agent.

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

Parameters4/5

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

Schema coverage is 100% and the schema already describes `payment` as a base64 x402 payload. The description still adds value by explaining the parameter's role in the two-step handshake — omitting it yields terms rather than a purchase — which the schema alone does not convey.

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 says it returns 'Agent-bond pools as the page lists them' and names its exclusions ('Does not deposit, cover or slash'), but it never states concretely what an agent-bond pool record is or what underwriting means here. The verb is absent — 'underwrite' appears only in the tool name — and the substantive definition is delegated to an external URL, so the agent must guess at the resource.

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 two-phase flow is spelled out precisely: call once without `payment` for terms, sign with your own wallet, then call again with `payment` to complete. It does not, however, describe when this tool is preferable to pool-related siblings such as arc_pools or dex_new_pools, so there is no exclusion guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources