Skip to main content
Glama

compare_chain_fees

Compare transfer fees across all supported chains for a token. Identifies the cheapest chain. No authentication required.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations are empty, so the description carries the full behavioral burden. It usefully discloses that no authentication is required and that comparison spans all supported chains, but it omits what is returned (per-chain fee breakdown vs just a winner), whether the values are live quotes or estimates, and whether any cost is incurred. That is a meaningful gap for a zero-annotation tool.

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 short sentences, front-loaded with the core action and outcome, with no redundant wording. The authentication note is compact and non-duplicative since no annotations exist.

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?

There is no output schema and no annotations, so the description is the only source of behavioral detail. It establishes purpose and scope but leaves the token-selection mechanism and the shape of the comparison result unexplained, which are material for correct invocation and result interpretation.

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?

With zero parameters the baseline would be 4, but the description introduces a 'for a token' qualifier that has no corresponding input, leaving the agent unable to determine how the token is specified. This unresolved reference lowers the score below the zero-parameter baseline.

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 description gives a specific verb and resource — compare transfer fees across all supported chains — plus a stated outcome, identifying the cheapest chain. It does not distinguish itself from nearby tools such as estimate_gas or get_payment_quote, which also concern fee/cost estimation, so an agent cannot fully disambiguate on the description alone.

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?

Usage is only implied: 'Identifies the cheapest chain' suggests the tool is for chain-selection decisions, but the description never states when to prefer it over estimate_gas or get_payment_quote, nor any exclusions. There are no prerequisites or context conditions given.

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