Skip to main content
Glama

MCP Apps Interactive DeFi, Polymarket & RWA Checkout Terminal UI

Build Institutional Delta-Neutral & Bridge Execution Dossier ($0.009 USDC via x402)

build_institutional_net_carry_dossier_x402
Read-onlyIdempotent

Generates an execution-ready delta-neutral carry matrix (4-leg fee break-even hours, Pendle fixed vs floating edge, and live LI.FI USDC bridge route). $0.009 a call, paid with x402 (USDC on Base eip155:8453, saves ~45K raw market feed tokens).

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

Input Schema

NameRequiredDescriptionDefault
holdDaysNoTarget holding period in days (default 30)
positionUsdNoPortfolio notional in USD (default 25000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, open-world, non-destructive), so the description's main added value is the payment behavior: $0.009 per call via x402, settled in USDC on Base (eip155:8453). That is a genuinely important operational fact not present in the annotations. It still omits what happens on payment failure or how long generation takes, which keeps it from a 5.

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

Conciseness4/5

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

A single tightly packed sentence that front-loads the purpose and then appends the cost and token-savings justification. Every clause carries information, though the title duplicates the price and the parenthetical list is dense. Minor redundancy between title and description price, but no wasted prose.

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?

With no output schema, the description correctly compensates by naming the three outputs an agent will receive. It also discloses the payment rail and chain. The remaining gap is that 'execution-ready' is ambiguous — it does not say whether the result includes signable calldata or only a recommendation matrix.

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?

Schema description coverage is 100% — holdDays and positionUsd are each documented with defaults — so the schema carries parameter meaning. The description adds only indirect signal (fee break-even hours relates to holdDays, portfolio scale relates to positionUsd) with no format, bounds, or unit clarification beyond the schema. Baseline 3 applies.

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 definition uses a specific verb ('Generates') and names a concrete artifact — an execution-ready delta-neutral carry matrix — then enumerates its parts (4-leg fee break-even hours, Pendle fixed vs floating edge, live LI.FI USDC bridge route). That is far more than a restated name. It stops short of a 5 because it never distinguishes this composite dossier from overlapping siblings such as compare_pendle_fixed_vs_funding or quote_crosschain_usdc_bridge, which produce some of the same components individually.

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

Usage Guidelines2/5

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

Nothing in the description states when to choose this over the sibling quote/compare tools, nor when not to. The only hint is a value proposition ('saves ~45K raw market feed tokens'), which implies it is a cheaper aggregate of feeds but is not framed as usage guidance. An agent has to infer selection criteria from the tool name alone.

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.