Skip to main content
Glama
Sign In
Bridge Metrics MCP

Bridge Metrics MCP

by kukapay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_chains

Fetch blockchain chains sorted by TVL descending. Returns name, Gecko ID, token symbol, chain ID, and TVL.

Instructions

Fetch and return a list of all chain slugs from DeFiLlama in a table format, sorted by TVL in descending order.
No parameters required.
Returns a table of chains data with columns: name, gecko_id, tokenSymbol, chainId, tvl.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 fully carries behavioral disclosure. It specifies the return format (table with columns) and ordering (TVL descending). It doesn't mention potential errors or latency, but for a read-only list, this is adequate.

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 sentences, front-loaded with the main action, then parameter info, then output details. No wasted words, highly efficient.

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?

For a simple list tool with no parameters and an output schema, the description covers everything: what it returns, the format, and the sorting. No gaps.

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?

No parameters exist, so the schema coverage is 100%. Following the baseline rule (0 params = baseline 4), the description adds no extra parameter semantics but isn't needed.

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?

The description clearly states it fetches a list of all chain slugs from DeFiLlama in table format, sorted by TVL. This distinguishes it from sibling tools like get_transactions or list_bridges.

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?

It explicitly says 'No parameters required,' guiding the agent that no input is needed. It doesn't discuss when to use vs alternatives, but the simplicity makes this sufficient.

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