Skip to main content
Glama
Sign In
feegate-yield-mcp

feegate-yield-mcp

by BrianTian818
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_chains

Discover chains with DeFi yield pools, including pool counts and total TVL, so you can select a chain before fetching individual pools.

Instructions

List all chains that have DeFi yield pools, with pool counts and total TVL. Use this first to discover which chains are available before calling get_pools.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it does disclose the returned fields (chain list, pool counts, total TVL) and that this is a discovery/read operation. It says nothing about ordering, pagination, caching, or whether the list is static, which would matter more for a catalog endpoint.

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?

Two sentences with no filler: the first defines the output, the second defines call order. The routing instruction to get_pools is front-loaded rather than buried.

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?

For a zero-parameter discovery tool with no output schema, the description adequately covers both what comes back and where it fits in the workflow. Minor gap: it does not indicate list size or whether results are ordered, though this is low-risk for a chain catalog.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the schema coverage is 100% by definition. The baseline of 4 applies since nothing about invocation is ambiguous.

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 and resource ('List all chains that have DeFi yield pools') and adds the payload shape ('pool counts and total TVL'). It is clearly distinguishable from get_pools and get_project_yields, which operate at pool and project granularity.

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?

Explicitly prescribes when to call it ('Use this first to discover which chains are available before calling get_pools'), giving a concrete ordering constraint against a named sibling. It stops short of stating any when-not conditions or what to do if a chain of interest is absent.

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