stake.link Agents (stakedotlink.money)

sdl_search_protocol

Protocol knowledge search with cited entry matches.

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": {
      "query": "<query>"
    },
    "name": "sdl_search_protocol"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum matches to return.
`query`	Yes	Natural language stake.link question or keyword.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 12, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden, but only hints that results are 'cited entry matches.' It does not state read-only safety, authentication requirements, ranking behavior, limits, or pagination, leaving most operational traits undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short and front-loads the core action, so it is not verbose. However, it is a bare noun phrase rather than a well-structured directive, and its extreme brevity edges into under-specification.

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 an unannotated search tool with no output schema, the description is too sparse. It does not explain how to use the tool vs. the many get_* siblings, what protocol corpus is searched, or what the cited results actually contain, so an agent lacks enough context to invoke it confidently.

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%, and the schema itself documents both 'query' and 'limit' clearly. The description adds no parameter meaning beyond what the schema already provides, so the baseline of 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 verb+resource ('search' + 'protocol knowledge') and adds the nature of the results ('cited entry matches'). It is clear enough to distinguish from the many build_* and get_* siblings, though it does not explicitly name an alternative or scope the protocol further.

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?

The description gives no when-to-use guidance, no prerequisites, and no alternatives among the numerous sibling tools. It implies a search use case but leaves all routing decisions to the agent.

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?