Skip to main content
Glama

rwa_yield

πŸ”’ PREMIUM (not available anonymously on this endpoint): Tokenized treasury and Real World Asset yields β€” BlackRock, Ondo, Maple, Centrifuge, Goldfinch and more. The institutional DeFi layer.

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

Input Schema

NameRequiredDescriptionDefault
limitNoResults (default: 15)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose one genuinely important trait: the endpoint is gated and unavailable anonymously. Beyond that it says nothing about what auth is needed, result ordering, pagination, or what the call returns, which is thin for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded β€” the access restriction leads, which is the right priority. But the closing tagline 'The institutional DeFi layer.' is pure marketing and earns no place, and the emoji-lock badge is decoration rather than signal.

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 one-optional-parameter list tool this is close to sufficient: the agent knows the asset class, the coverage breadth, and that credentials are required. With no output schema, though, the absence of any hint about returned fields (APY, TVL, protocol, chain) leaves a gap an agent would want filled.

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?

There is a single optional parameter and the schema already describes it at 100% coverage ('Results (default: 15)'), so the description cannot be expected to re-document it. It adds no meaning about what a result unit is (a pool? a protocol? an asset?), leaving the limit's effect on payload ambiguous.

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 names a specific resource domain β€” tokenized treasury and Real World Asset yields β€” and lists concrete providers (BlackRock, Ondo, Maple, Centrifuge, Goldfinch), which distinguishes it from siblings like chain_yields and stablecoin_yield by asset class. It never states a verb (list/scan/fetch), so the agent must infer that this returns yield data rather than computing or comparing it.

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 'PREMIUM (not available anonymously on this endpoint)' note is a real usage condition that tells an agent an unauthenticated call will fail. However, there is no guidance on when to pick this over yield_scan, top_yields, risk_adjusted, or yield_compare, and no exclusion rules; the choice is left to inference from the asset-class label.

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.