stake.link Agents (stakedotlink.money)

sdl_get_contract_source

Fetch the verified Solidity source for a live stake.link contract from Sourcify.

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": {
      "contract": "<contract>"
    },
    "name": "sdl_get_contract_source"
  }
}

Input Schema

Name	Required	Description
`contract`	Yes	Contract id, name, or address.
`file_path`	No	Optional specific Solidity file path.
`include_all_files`	No	Include all verified source files.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 12, 2026

TDQS

B3.3/5.0

Behavior3/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 does add useful provenance context ('verified' via Sourcify), implying a trusted read-only fetch, but says nothing about behavior for unverified contracts, error conditions, or rate limits.

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

Conciseness5/5

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

A single well-formed sentence with the key scope and source front-loaded; no filler or redundancy.

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?

For a read-only lookup with no output schema, the description omits what is actually returned (single contract source vs. all files, and how file_path/include_all_files affect the result). It is workable given the schema hints, but not fully complete.

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 all three parameters are already documented in the schema. The description adds no syntax or format detail beyond that, which is the expected baseline when the schema does the heavy lifting.

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 (Fetch), resource (verified Solidity source), scope (live stake.link contract), and provenance (Sourcify). It is distinguishable from siblings like sdl_get_contract_abi by emphasizing source code rather than ABI, though it doesn't explicitly name those siblings.

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 guidance on when to choose this over sdl_get_contract or sdl_get_contract_abi, and no stated prerequisites or exclusions. Usage is only weakly implied by the word 'source'.

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?