Skip to main content
Glama
Sign In
Regen Network MCP Server

Regen Network MCP Server

by gaiaaiagent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_delegation_rewards

Fetch delegation rewards for a specific delegator-validator pair on the Regen Network blockchain, enabling portfolio tracking and reward analysis.

Instructions

Get delegation rewards for specific delegator-validator pair.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "delegator_address": "<delegator_address>",
      "validator_address": "<validator_address>"
    },
    "name": "get_delegation_rewards"
  }
}

Input Schema

NameRequiredDescriptionDefault
delegator_addressYes
validator_addressYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior but only states it is a read operation. It does not mention authentication, error handling, or what happens if the pair does not exist.

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?

Single sentence, clear and concise. No unnecessary words. Efficiently conveys the core purpose.

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 having an output schema, the description lacks guidance on when to use, behavioral details, and parameter semantics, making it incomplete for effective tool selection.

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%, but the description only vaguely refers to 'specific delegator-validator pair' without explaining address format or constraints. Minimal added meaning beyond parameter names.

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?

The description clearly uses a specific verb and resource ('Get delegation rewards') and identifies the pair, distinguishing it from siblings like get_delegation_total_rewards or get_validator_outstanding_rewards.

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 like get_delegation_total_rewards or get_validator_outstanding_rewards. No context on prerequisites or use cases.

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

Deploy Server

Other Tools