Skip to main content
Glama

Wicked MCP

by io.github.choaticpixels
OverviewDiscussionsAdmin

registry_search_tools

Search Wicked Registry for x402/MCP tools by real, live reliability data (uptime, latency, schema conformance — never fabricated).

Works unauthenticated via x402 (a 402 response carries payment
instructions in its body) or with a free-tier key set via
REGISTRY_API_KEY.

Args:
    category: Filter by category, e.g. "data", "crypto".
    protocol: Filter by protocol — "x402", "mcp", or "rest".
    min_score: Minimum composite score (0-100). Tools with no check
        history yet are excluded once this is set, rather than treated
        as a 0.
    sort: One of "score" (default), "latency", "recency".
    limit: Max results, 1-200. Defaults to 50.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoscore
limitNo
categoryNo
protocolNo
min_scoreNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well: it discloses the two auth modes (402 payment instructions in body, or REGISTRY_API_KEY), and notably explains that min_score excludes tools with no check history rather than treating them as 0. It does not cover rate limits or destructive potential, but this is a read operation.

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?

The description is front-loaded with purpose and auth, then uses a clean Args list. Slightly verbose in places (the parenthetical about fabrication and payment instructions), but each line carries information and nothing is padding.

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?

Given five optional params and an existing output schema (so return values need not be described), the definition is nearly complete. It covers auth, filtering, sorting, and limiting; the only mild gap is lack of explicit sibling differentiation.

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: it documents every parameter with meaning, including concrete category and protocol examples, the actual protocol enum values (x402/mcp/rest), sort values, the limit range (1-200), and the non-obvious min_score exclusion semantics.

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?

The description states a specific verb and resource (search Wicked Registry for x402/MCP tools) and clarifies the differentiator (real, live reliability data, never fabricated). It is clear, though it does not explicitly name how it differs from siblings like registry_featured_tools or 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 Guidelines3/5

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

Usage context is implied rather than stated: the auth paths (unauthenticated via x402 vs free-tier key) suggest when the tool works, but there is no explicit when-to-use or when-not-to-use guidance relative to the registry sibling tools.

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

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