Wicked MCP

registry_register_tool

Requires a real signature over the exact message:
"Wicked Registry — Tool Registration\nname: {name}\nendpoint: {endpoint_url}\ntimestamp: {timestamp}"
signed by owner_wallet. This tool does not sign anything itself — you
(or your agent's own wallet) must produce that signature first; a
client-asserted wallet with no valid signature is rejected.

Args:
    name: Tool name.
    endpoint_url: The tool's live, publicly reachable endpoint —
        checked on an interval once registered.
    protocol: One of "x402", "mcp", "rest".
    category: Free-text category, e.g. "data", "crypto".
    description: What the tool does.
    owner_wallet: The 0x wallet address that signed the registration message.
    signature: The 0x-prefixed ECDSA signature over the registration message.
    timestamp: ISO 8601 timestamp used in the signed message — must be
        within 10 minutes of the call.
    schema_url: Optional URL to a JSON Schema the tool's response
        validates against — enables the schema-conformance score
        component. Omit if the tool doesn't publish one.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`category`	Yes
`protocol`	Yes
`signature`	Yes
`timestamp`	Yes
`schema_url`	No
`description`	Yes
`endpoint_url`	Yes
`owner_wallet`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description carries full behavioral burden and delivers: it does NOT sign on your behalf, unsigned/client-asserted wallets are rejected, the endpoint is polled on an interval, the timestamp must be within 10 minutes, and schema_url toggles a score component. This is rich, non-obvious operational context.

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?

Front-loaded with purpose, then the signing prerequisite, then Args. Every line earns its place, though the verbatim signature-message block and repeated 0x/format notes add some bulk that could be marginally tighter.

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

Completeness5/5

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

For a 9-param, 8-required mutation tool with no annotations but an output schema, the description covers purpose, auth/signature flow, timing constraints, and all parameter meanings. Return values are covered by the output schema, so nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does—every one of the 9 params is explained, including the exact signed-message template, protocol enum values ("x402", "mcp", "rest"), timestamp window, and that schema_url is optional with a specific effect.

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

Purpose5/5

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

Specific verb+resource ("Register a tool... with Wicked Registry") plus the concrete benefit ("real synthetic checks and a live reliability score"). It is clearly distinguishable from sibling registry tools like registry_search_tools, registry_report_tool, and registry_tool_detail.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States clear context (you must own the tool, and you must produce a valid signature first) and gives the rejection condition for missing signatures. It does not explicitly name alternative siblings or when-not-to-use, so it falls short of a 5.

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

All Wicked MCP 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.