Skip to main content
Glama

x402-services

by ai.firmbrain

crypto_yields

Top DeFi yield opportunities across chains from DeFiLlama, filterable by chain/project/min-TVL, ranked by APY. Send { chain?, project?, minTvl?, limit? }. Yield discovery for finance agents. [x402 paid tool — price $0.003; POST /api/crypto/yields]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoFilter by chain, e.g. Base, Ethereum
limitNoMax pools, default 10 (max 50)
minTvlNoMinimum pool TVL in USD (default 1,000,000)
projectNoFilter by protocol, e.g. aave

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist. Description adds cost ($0.003), HTTP method (POST), and endpoint, which is helpful. However, it doesn't explicitly state read-only nature or idempotency.

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 efficient sentences: first explains purpose, second shows usage. No fluff, all information earns its place.

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?

Given no output schema, the description adequately explains source, filtering, ranking, and payment. Could mention output format but overall complete for a simple data retrieval tool.

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 100%, and the description adds default values (limit default 10, minTvl default 1,000,000) not in the schema. Also shows compact optionality syntax.

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?

Clearly states it fetches top DeFi yield opportunities from DeFiLlama, filterable by chain/project/min-TVL, ranked by APY. This distinguishes it from siblings like rh_yields and other crypto tools.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs alternatives like rh_yields. The description only hints at usage with 'Yield discovery for finance agents', but lacks when-not or alternative names.

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

All x402-services toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation4/5

Tools are organized by domain prefix (e.g., 'crypto_', 'rh_', 'snipe_'), which helps distinguish between areas. Within each domain, they serve distinct purposes, though some overlap between domains exists (e.g., price data appears in multiple groups). Overall, an agent can navigate effectively.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern with a domain prefix and a verb_noun combination (e.g., 'compliance_risk', 'rh_stock', 'snipe_honeypot'). This makes the API predictable and easy to explore.

Tool Count2/5

With 159 tools, the server is extremely large. While the broad scope of web3 and utility functions justifies many tools, the count is significantly above the typical range for a coherent toolkit, potentially overwhelming agents and increasing selection error.

Completeness4/5

The toolkit covers a wide range of web3 operations: crypto, DeFi, compliance, safety, scheduling, memory, etc. There are no obvious major gaps for its intended purpose, though some niche areas might be missing.

Resources