Skip to main content
Glama
Sign In

Feegate AI Agent data marketplace catalog & platform metrics

by org.feegate
OverviewDiscussionsAdmin

stablecoin-yield.by_chain

Read-onlyIdempotent

Ask "which stablecoin pool has the best risk adjusted yield" — full: top 20 risk-adjusted pools filtered to one chain. ｜ 按链查智能排名 Top20（链名如 Ethereum / Arbitrum / Base）：该链风险调整后的最优稳定币池

[zh] 供应方资产「稳定币最高收益池榜（跨链实算）」按次计费 $0.1 USDC（或等值积分）。 入参：chain。 [en] Vendor asset "稳定币最高收益池榜（跨链实算）". Paid per call: $0.1 USDC (or prepaid credits). Args: chain. 付款/支付头在 MCP 请求头里带（X-Payment / X-Payment-Tx / Authorization: Bearer fg_…），不要放进参数。

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": {
      "chain": "<chain>"
    },
    "name": "stablecoin-yield.by_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-structured context: paid per call at $0.1 USDC or prepaid credits, with X-Payment / X-Payment-Tx / Bearer headers carried in the MCP request headers rather than in the parameters — a real invocation constraint. It says nothing about return shape or ranking methodology, which matters since no output schema exists.

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?

The first clause is well front-loaded and the payment constraint is placed after the purpose. However, the same content is restated across English, Chinese, and a bilingual vendor-asset block ('跨链实算', 'Vendor asset'), so a meaningful share of the text is duplication rather than new information.

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 one-parameter read-only tool this covers purpose, parameter examples, and payment mechanics, which is most of what an agent needs. With no output schema, it should have sketched what a 'risk-adjusted pool' entry contains or pointed to the yield_methodology sibling; that gap is left open.

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?

Schema coverage is 0% for the single 'chain' parameter, so the description must carry the burden, and it does supply concrete value examples ('Ethereum / Arbitrum / Base'). It still does not state casing rules, accepted chain identifiers, or whether unknown chains error, leaving some ambiguity.

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 opening line states a concrete verb and resource: 'top 20 risk-adjusted pools filtered to one chain', which an agent can distinguish from the unfiltered top20 sibling by the chain filter. It stops short of naming that sibling explicitly, so the differentiation is inferred 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 Guidelines3/5

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

The phrasing 'Ask "which stablecoin pool has the best risk adjusted yield"' implies the question this tool answers, giving usable context. There is no explicit when-not guidance and no named alternative (e.g. the cross-chain top20) for an agent that does not have a chain in hand.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Feegate AI Agent data marketplace catalog & platform metrics toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources