scdo-agent-plugins

by SCDOLAB

Overview Schema Source Related Servers Discussions Admin

Python

Local

Ledger ERC-8004 registration

ledger_registration

Read-only

Retrieve ERC-8004 registration documents for the Agent Ledger and main SCDO agent, including services and endpoints.

Instructions

ERC-8004 registration documents of the Agent Ledger and of the main SCDO agent (services, endpoints).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ledger_registration"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered externally. The description adds that the returned documents concern the Agent Ledger and the main SCDO agent (services, endpoints), which is useful scoping, but says nothing about result shape, size, or what 'SCDO agent' refers to given there is no output schema.

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 compact sentence with no filler or redundancy. It is front-loaded and efficient, though the heavy jargon (ERC-8004, SCDO) makes it slightly opaque rather than maximally clear.

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 no-argument, read-only tool with no output schema, the description carries the burden of describing the return. It gestures at content (registration documents, services, endpoints) but does not explain structure, so an agent knows roughly what it gets but not the shape or how to use the result.

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?

The tool takes zero parameters, so the schema needs no elaboration and the baseline of 4 applies. Nothing in the description is required to clarify inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource (ERC-8004 registration documents of the Agent Ledger and the main SCDO agent) and hints at content (services, endpoints), so an agent can infer it is a lookup of registration metadata. However, it is a verbless noun phrase and does not distinguish itself from sibling ledger tools such as ledger_get_agent or register_agent, leaving the exact action ambiguous.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives despite several adjacent ledger tools (ledger_stats, ledger_list_agents, ledger_get_agent) and register_agent. The agent must infer the trigger condition on its own.

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