Skip to main content
Glama
Sign In
Wicked MCP server

Wicked MCP server

by WickedAPI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

reputation_status

Read-onlyIdempotent

Fetch an agent’s current reputation—tier, active and unbonding stake, score, slash count, and founding-member badge—before interacting; treat a 404 as unranked.

Instructions

[Wicked Reputation] An agent's current reputation: tier, active/unbonding stake, score, slash count, founding-member badge. http_status 404 means the wallet never registered — treat as tier 'unranked'.

Use when you want one agent's tier, stake, reputation score and slash count before dealing with it. Not for the event history (use reputation_statement) or a ranking (use reputation_leaderboard).

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": {
      "wallet": "<wallet>"
    },
    "name": "reputation_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesThe 0x wallet address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnlyHint/idempotent/openWorld, so the 'Behavior: read-only' line adds nothing new. However, the http_status 404 semantics — that an unregistered wallet returns 404 and should be interpreted as 'unranked' rather than an error — is a genuinely valuable behavioral disclosure an agent would otherwise mishandle.

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 what is returned, then when-to-use, then alternatives, then behavior — a sensible ordering with no wasted prose. The closing 'Behavior: read-only' line is redundant with the readOnlyHint annotation and could be dropped.

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?

With no output schema, the description compensates well by enumerating the returned fields and by defining the 404 case. Minor gaps remain (no indication of what an 'unbonding' stake looks like or the score's range/units), but nothing essential for correct invocation is missing.

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?

Single parameter with 100% schema description coverage ('The 0x wallet address'), so the schema carries the load and baseline 3 applies. The description implies the wallet identifies a single agent but adds no format, validation, or case-sensitivity detail beyond the schema.

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?

Names a specific resource (an agent's reputation) and enumerates exactly what is returned: tier, active/unbonding stake, score, slash count, founding-member badge. It also distinguishes the tool from reputation_statement and reputation_leaderboard by name, so an agent can route without opening any 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?

Explicit when-to-use ('before dealing with it') plus two explicit exclusions naming the correct sibling for each alternative use case. The 404 edge case is also given a decision rule ('treat as tier unranked'), which removes the main ambiguity an agent would hit.

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