stake.link Agents (stakedotlink.money)

sdl_get_priority_pool_wallet

Priority Pool wallet inclusion, queue share, and claimable state for an address.

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": {
      "address": "<address>"
    },
    "name": "sdl_get_priority_pool_wallet"
  }
}

Input Schema

Name	Required	Description	Default
`pool`	No	Priority pool. Default LINK.
`address`	Yes	Ethereum wallet address.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 12, 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 carries the full burden. It is a read query on public chain state, yet the description never states that it is read-only, does not require auth, or has no side effects. It also does not describe return shape or whether queue share is a percentage or raw amount.

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 front-loaded noun phrase naming the three returned metrics and the subject. Efficient, though it is a fragment rather than a sentence and omits any usage clause.

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

Completeness3/5

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

With no annotations and no output schema, the description needs to explain the return values and read-only nature. It names the three metrics but leaves units, format, and behavior for an invalid address or unknown wallet unexplained.

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%: address is documented as an Ethereum wallet address and pool as an enum defaulting to LINK. The description adds no parameter-level detail beyond the schema, so baseline 3 is appropriate.

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?

States a specific resource and scope: priority pool wallet inclusion, queue share, and claimable state for an address. An agent can distinguish it from sdl_get_priority_pool (pool-level) and sdl_get_priority_pool_distribution, though the difference from sdl_get_priority_pool_batch_compare is not spelled out.

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, no exclusions, and no mention of alternatives like sdl_get_priority_pool or sdl_get_priority_pool_batch_compare, which occupy adjacent territory. The agent must guess which of the priority-pool siblings to call.

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

All stake.link Agents (stakedotlink.money) 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?