Skip to main content
Glama

Stratalize Intelligence

Get Rwa Benchmark

get_rwa_benchmark
Read-only

Real-world asset tokenization benchmarks — tokenized T-bill yields (Ondo, BlackRock BUIDL, Superstate, Franklin Templeton), RWA market TVL by category, YoY growth. $12.8B total RWA market. Source: DeFiLlama + public data. $0.02 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

The annotations already establish read-only, open-world, non-destructive behavior, so the description's main addition is the $0.02 USDC per-call cost and the DeFiLlama plus public-data provenance, both of which materially affect invocation decisions. It omits data freshness/update cadence and return shape, which keeps it short of a 5.

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 description is dense and front-loaded with the differentiating content first, and almost every clause carries information. The static '$12.8B total RWA market' figure is the weakest element since it will date quickly and does little to aid tool selection.

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-optional-parameter tool with an output schema absent, the description covers data sources and headline metrics reasonably well. It still leaves the agent guessing about default category behavior, response granularity, and data recency, which are meaningful gaps for a paid, open-world data tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single `category` parameter receives no explanation in the description. The enum values are largely self-explanatory, and the mention of 'TVL by category' hints at segmentation, but 'real_estate' and 'credit' are never mapped to content, and the default behavior when `category` is omitted is unstated.

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 uses a specific verb-plus-resource framing and enumerates concrete content: tokenized T-bill yields from named issuers, RWA market TVL by category, and YoY growth. That makes it clearly distinguishable from siblings like get_defi_yield_benchmark or get_chain_tvl_benchmark, though it never explicitly contrasts itself with them.

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?

There is no when-to-use or when-not-to-use guidance anywhere in the text. An agent must infer from the data providers listed that this is for real-world-asset tokenization rather than general DeFi yield or chain TVL, and nothing steers it away from the closely related benchmark siblings.

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.

Resources