Skip to main content
Glama
Sign In
Steward MCP

Steward MCP

by brianbooms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

steward_cheapest_route

Compare live fees for six USDC/BTC transfer routes by USD amount, return the lowest-cost option and ranked list. Read-only advisory; no wallet, no custody.

Instructions

Cheapest of 6 crypto transfer routes for a USD amount — USDC on Base, Solana, Polygon, Arbitrum, Avalanche C-chain, and BTC — ranked with live fee data. Returns the ranked list plus the single cheapest route. Use this for a quick answer; use steward_route_fees for the full fee table. Advisory only: neutral ranking, no wallet, no custody, moves nothing. Free, read-only.

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": {
      "amount_usd": "<amount_usd>"
    },
    "name": "steward_cheapest_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoOptional: restrict to one token — 'USDC' or 'BTC'. Omit to compare all routes.
amount_usdYesTransfer amount in USD, 1-100000 (e.g. 250).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses 'live fee data', 'Advisory only: neutral ranking, no wallet, no custody, moves nothing', and 'Free, read-only', which is the key safety profile. It does not cover latency, caching, or fee-source freshness, so it falls just short of complete.

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?

Three tight sentences, front-loaded with the core purpose, then the sibling routing note, then the safety caveat. No filler; each clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by stating the return shape ('the ranked list plus the single cheapest route'). Combined with the advisory/read-only framing, an agent has everything needed to call it correctly.

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% (both amount_usd range and the token restriction are documented in the schema), so the baseline is 3. The description adds only the amount's USD framing and route scope, no syntax or semantics beyond the schema.

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?

States a specific verb+resource (cheapest of 6 crypto transfer routes for a USD amount) and enumerates the exact route set, so the agent knows precisely what is compared. It is clearly distinguishable from steward_route_fees, which it names.

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

Usage Guidelines5/5

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

Explicitly instructs: 'Use this for a quick answer; use steward_route_fees for the full fee table.' This gives both the when-to-use condition and the named alternative, leaving nothing to inference.

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