Skip to main content
Glama

stake.link Agents (stakedotlink.money)

sdl_get_reward_history

Reward distribution history from the LinkPool subgraph.

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

Input Schema

NameRequiredDescriptionDefault
poolNoPool to query.
limitNoNumber of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says the data comes from a subgraph; it doesn't state whether results are paginated, ordered, time-scoped, or what happens with no/partial parameters. Minimal behavioral disclosure for a data-fetch tool.

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?

A single short sentence, front-loaded with the resource and source. Efficient, though it could have used the space to add behavioural or usage context.

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?

For a two-parameter data tool with no annotations and no output schema, the description omits return shape, pagination, scope, and usage context. It is under-specified for its complexity.

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?

Schema description coverage is 100%, so the schema already documents 'pool' and 'limit' including the enum. The description adds nothing beyond the source, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb-ish resource ('Reward distribution history') and a specific data source (LinkPool subgraph), so the resource is clear. But it doesn't differentiate from siblings like sdl_get_priority_pool_distribution or sdl_get_sdl_tier_distribution, leaving the agent to infer scope.

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 when-to-use guidance and no mention of alternatives among many similar distribution/reward siblings. The agent gets no signal about when this is the right tool versus the other pool/distribution 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