Skip to main content
Glama

Non-Custodial EVM DEX Swap Router, Sniper Calldata & Hyperliquid MCP

Build Institutional Delta-Neutral & Bridge Execution Dossier ($0.01 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.01 a call, paid with x402 (USDC on Base eip155:8453).

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description does add genuinely valuable non-obvious context beyond them: every call costs $0.01 USDC on Base (eip155:8453) via x402, which an agent must know before invoking. It still doesn't say whether the tool performs live external network calls that can fail, or how latency/rate behavior works for a paid endpoint.

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?

Two tight sentences, with the artifact described first and the price/payment mechanism second, so the important part is front-loaded. The parenthetical content list is dense but each element earns its place by signalling the sections of the output.

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 2-parameter, read-only tool with no output schema, the description covers cost and rough output contents, which is the most an agent needs to decide to call it. However, since there is no output schema, the description should do more to say what the dossier actually looks like when returned (report shape, whether the bridge route is executable or informational).

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%, with both holdDays and positionUsd documented including defaults, so the schema already carries the semantics. The description adds nothing about how holdDays interacts with the '4-leg fee break-even hours' output or how positionUsd scales the matrix, so 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?

A concrete verb ('Generates') plus a specific artifact ('execution-ready delta-neutral carry matrix') with the three contents enumerated (4-leg fee break-even hours, Pendle fixed vs floating edge, live LI.FI USDC bridge route). It is clearly distinguishable in substance from the single-purpose siblings, but it never states that relationship explicitly, so the differentiation is left to inference rather than stated.

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?

The description says what the tool produces but never says when to reach for it instead of the narrower siblings such as compare_pendle_fixed_vs_funding or quote_crosschain_usdc_bridge. There is no guidance on preconditions, no 'use this when you want a full composite dossier versus a single-leg quote', and no exclusions.

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.