Regen Network MCP Server

get_denoms_metadata

Retrieve comprehensive metadata for all tokens on the Regen Network blockchain, enabling query of ecological credit and biodiversity asset details with pagination support.

Instructions

Get metadata for all tokens.

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_denoms_metadata"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`limit`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 27, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the burden. It only says 'Get metadata for all tokens' but does not disclose that the tool supports pagination via page and limit parameters, or any behavioral traits like rate limits or data freshness. The agent cannot infer pagination behavior from the description.

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 a single concise sentence. It is front-loaded and wastes no words. However, it could be slightly improved by mentioning pagination without adding much length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite an output schema existing, the description is too minimal. It fails to mention that the tool returns a paginated list, how to control pagination, or what constitutes a 'token' metadata. For a tool with two optional parameters, the description should provide at least basic context about its usage.

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%, so description must explain parameter meanings. It does not mention page or limit parameters, leaving the agent to infer their purpose from names alone. While 'page' and 'limit' are somewhat self-explanatory, the description adds no value beyond the schema.

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?

Description clearly states 'Get metadata for all tokens,' which distinguishes it from sibling 'get_denom_metadata' that gets metadata for a single token. The verb 'Get' and resource 'metadata for all tokens' are specific and unambiguous.

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 guidance on when to use this tool versus alternatives. It does not mention that pagination parameters exist or when to prefer this over get_denom_metadata or other list tools. The description merely states what it does without context.

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

Deploy Server