Realtap

Stake pool detail

get_stake_pool

Read-onlyIdempotent

One Cardano stake pool: name, ticker, status, margin (percent), fixed cost and pledge (ADA), live and active stake (ADA), saturation (percent), delegators, blocks minted, estimated and recently realised yearly return (percent), description and homepage. performance lists its last finished epochs (blocks minted against blocks expected from its stake, luck in percent, the return delegators got) and says how many epochs are on record. Pass stakeAda to also get rewardEstimate: the ADA that amount is expected to earn per epoch and per year in this pool, with what the estimate assumes.

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": {
      "poolId": "<poolId>"
    },
    "name": "get_stake_pool"
  }
}

Input Schema

Name	Required	Description	Default
`poolId`	Yes	Bech32 pool id (pool1…) or its 56-hex form. Get it from `search` or `list_stake_pools`.
`stakeAda`	No	Optional amount of ADA to delegate: adds an estimate of its staking reward in this pool.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the shape of the nested `performance` block, that it reports how many epochs are on record, and what the reward estimate assumes. It omits error behavior for an unknown/resolved pool id.

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?

Front-loaded with identity and the core field list, then the conditional `stakeAda` behavior. The dense field enumeration is long but earns its place as a stand-in for the absent output schema; a light trim of the top-level field list would make it tighter.

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

Completeness5/5

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

With no output schema, the description carries the full burden of describing returns, and it does so for both the top-level pool object, the nested `performance` array, and the conditional `rewardEstimate`. Nothing an agent needs in order to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% so the baseline is 3, but the description goes further by explaining what `stakeAda` actually unlocks (per-epoch and per-year ADA returned, plus stated assumptions), which the schema's one-line parameter description does not convey.

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?

Opens with a specific verb+resource ('One Cardano stake pool') and then enumerates exactly which fields come back, which clearly separates it from list_stake_pools (collection listing) and the more general get_pool sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the conditional usage decision for the optional parameter clearly: 'Pass `stakeAda` to also get `rewardEstimate`', including what that estimate contains. It does not explicitly name when to prefer this over list_stake_pools or get_pool, so no exclusions/alternatives are given.

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

All Realtap tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?