Wicked MCP

reputation_query

Read-onlyIdempotent

[Wicked Reputation] Search/rank registered agents by tier, stake, reputation or slash history. Every filter is a typed query param.

Use when you want to filter or rank agents by tier, stake, reputation or slash history. Not for one known wallet (use reputation_status).

Behavior: read-only.

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": "reputation_query"
  }
}

Input Schema

Name	Required	Description
`sort`	No	stake_amount \| reputation_score \| slash_count \| registered_at, prefixed "-" (desc, default) or "+" (asc).
`tier`	No	Exact tier name, e.g. "gold".
`limit`	No	1-200, default 20.
`max_stake`	No	Maximum active stake (USDC).
`min_stake`	No	Minimum active stake (USDC).
`min_reputation`	No	Minimum reputation score.
`founding_member`	No	True to only show founding members.
`min_slash_count`	No	Minimum slash events (1 finds agents ever slashed).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the trailing 'Behavior: read-only.' line merely restates structured data. The description adds no behavioral context beyond that — no note on result size, pagination behavior, or the registry scope implied by openWorldHint. With annotations carrying the safety profile, this adds little.

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?

Three short, front-loaded blocks with no filler. Minor redundancy: the list 'tier, stake, reputation or slash history' appears in both the first and second sentences, so one sentence could be trimmed.

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 an 8-param filtered-list tool with full schema coverage, rich annotations, and no output schema, the description covers purpose, alternative routing, and safety posture. What remains thin is return-shape and pagination expectations, which are minor given the schema's limit/sort documentation.

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% and all 8 filter params are documented with units and ranges in the schema itself. The description only says 'Every filter is a typed query param,' which adds no semantics beyond what the schema provides, so the 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?

The description states a specific verb pair (search/rank) and resource (registered agents) plus the four filter dimensions, then explicitly rules out the sibling case with 'Not for one known wallet (use reputation_status).' An agent can distinguish it from reputation_status or reputation_leaderboard 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?

It gives both the when ('filter or rank agents by tier, stake, reputation or slash history') and the when-not with a named alternative ('use reputation_status'). Routing is unambiguous.

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.