Realtap

Pool or DRep page claim

get_entity_claim

Read-onlyIdempotent

Whether a stake pool or DRep page has been claimed by its operator, the verified links and description, and how an operator claims a page. Only a claim whose status is "verified" was proven with a key of the pool or DRep; "approved" means Realtap reviewed it, which is not a key proof.

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": {
      "kind": "<kind>",
      "id": "<id>"
    },
    "name": "get_entity_claim"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Bech32 id: pool1… for a pool, drep1… for a DRep. `get_stake_pool` and `get_drep` return it.
`kind`	Yes	pool or drep.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered. The description adds genuinely useful semantic context beyond the structured data: the distinction between a \"verified\" claim (proven with the operator's key) and an \"approved\" one (reviewed only), which is exactly the interpretive nuance an agent needs to report status correctly.

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?

Two sentences, front-loaded with what is returned, then the caveat about status values. Dense but every clause carries weight; the phrasing is noun-heavy rather than verb-led, which slightly slows comprehension.

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

Completeness4/5

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

For a two-parameter read-only lookup with no output schema, the description is adequately complete: it names the returned fields and, critically, clarifies the ambiguous status vocabulary. It could add one line on the relationship to get_stake_pool/get_drep but nothing essential is missing.

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 coverage is 100%, with the id format (pool1…/drep1…) and the kind enum fully documented in the schema. The description mentions the pool/DRep axis but adds no syntax or format detail beyond what the schema already supplies, so the baseline 3 applies.

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 the specific resource (a stake pool or DRep page claim) and enumerates what the response carries: claim status, verified links and description. It does not explicitly distinguish itself from the closely related siblings get_stake_pool and get_drep, leaving the agent to infer the split.

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?

Usage is only implied: the agent can infer this is the lookup for page-claim status, but there is no statement of when to call this versus get_stake_pool or get_drep, and no prerequisites or exclusions 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?