Skip to main content
Glama

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
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is known. The description adds useful context beyond that: data provenance (DeFiLlama + public data) and a per-call cost of $0.02 USDC, which is behaviorally relevant for an agent. However, it does not describe return format, rate limits, or error behavior, leaving some behavioral gaps.

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 front-loaded with the core purpose and packs supporting details (data sources, market size, cost) into a compact form. Every sentence adds some value, though the '$12.8B total RWA market' figure is more of a data point than a functional spec. It is appropriately sized for a simple read tool.

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 tool with one optional parameter, no output schema, and provided annotations, the description gives a reasonable overview of what data is returned and includes cost and source. However, it does not explain how the category parameter changes the output, nor does it describe the response structure, which is important given the absence of an output schema. It is adequate but has clear gaps.

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?

The single parameter 'category' has an enum with four values but 0% schema description coverage. The description alludes to 'TVL by category' and gives examples like 'tokenized T-bill yields' (roughly mapping to treasuries), but it does not explain the enum values real_estate, credit, or all, nor what selecting each does. With low schema coverage, the description should compensate more fully but falls short.

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 ('Real-world asset tokenization benchmarks') and enumerates the data it returns (tokenized T-bill yields, RWA market TVL by category, YoY growth), making the tool's scope clear. It does not explicitly differentiate itself from siblings like get_defi_yield_benchmark, but the RWA-specific content makes the distinct purpose evident.

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 description lists the data covered, which implies when the tool is useful (for RWA tokenization metrics), but it offers no explicit when-to-use or when-not-to-use guidance and does not name alternatives. An agent can infer relevance from the content list but must decide independently whether to prefer this over related benchmark tools.

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