Skip to main content
Glama
Sign In
Wicked MCP server

Wicked MCP server

by WickedAPI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

registry_tool_detail

Read-onlyIdempotent

Get a single registry tool's full score breakdown, component history, and recent real health checks by tool ID; use for tool due diligence, not discovery.

Instructions

[Wicked Registry] One tool's full score breakdown, component history and recent real health checks. x402 or a free API key.

Use when you want one tool's full score breakdown and recent real health checks. Not for finding tools (use registry_search_tools or registry_lookup).

Behavior: read-only.

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": {
      "tool_id": "<tool_id>"
    },
    "name": "registry_tool_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoFree Wicked Registry API key (wr_...). Overrides REGISTRY_API_KEY.
tool_idYesRegistry id from registry_lookup / registry_search_tools / registry_featured_tools.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.2
    • addedInput schema / properties / api_key
      Added value: +{
+  "description": "Free Wicked Registry API key (wr_...). Overrides REGISTRY_API_KEY.",
+  "type": "string"
+}
    • changedInput schema / properties / tool_id / description
      Previous value: -"Registry id from registry_search_tools / registry_featured_tools."New value: +"Registry id from registry_lookup / registry_search_tools / registry_featured_tools."
  2. First observedv0.3.1

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the closing 'Behavior: read-only' sentence merely restates them. The genuinely additive context is the access model — 'x402 or a free API key' — which tells the agent a payment or key may be needed. No info on how many health checks/history entries come back, but for a single-record read that is a modest gap.

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?

Short and front-loaded, with the capability stated first and routing second. The second sentence largely rephrases the first ('full score breakdown and recent real health checks' appears twice), which is mild redundancy rather than bloat.

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

Completeness4/5

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

For a two-parameter read-only detail tool with no output schema, the description tells the agent what it will get back (score breakdown, component history, health checks), how to authenticate (x402 or API key), and which siblings to use instead. It does not mention behavior on unknown tool_id or depth limits, which keeps it a small distance from 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 coverage is 100% and both parameters carry descriptions, including how to obtain tool_id. The description adds no format, prefix or override semantics beyond what the schema states, so baseline 3 applies.

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?

States a specific verb and resource — retrieving one tool's full score breakdown, component history and recent real health checks. The bracketed namespace plus the explicit contrast with registry_search_tools/registry_lookup make it distinguishable from siblings without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use clause (wanting a single tool's breakdown and health checks) and an explicit when-not-to-use clause that routes to the correct sibling tools. Nothing is left to inference about selection.

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

Deploy Server

Other Tools