Skip to main content
Glama
Sign In

Wicked MCP

by io.github.WickedAPI
OverviewDiscussionsAdmin

reputation_statement

Read-onlyIdempotent

[Wicked Reputation] An agent's full position plus real event ledger (stakes, unstakes, withdrawals, slashes). Does not include WickedAPI call volume or fees — see the note field.

Use when you need an agent's full position and ledger of stakes, unstakes, withdrawals and slashes. Not for a quick tier check (use reputation_status).

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_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesThe 0x wallet address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, so the description does not need to prove safety; it nonetheless adds a real scope boundary by excluding call volume and fees and redirecting the agent to the `note` field. The trailing 'Behavior: read-only' simply restates readOnlyHint, so it is slightly redundant but not contradictory.

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 the tool returns and an efficient exclusion note. The 'Use when...' sentence largely restates the opening inventory of stakes/unstakes/withdrawals/slashes, and 'Behavior: read-only' repeats structured annotation data, costing some words.

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?

No output schema exists, so the description must orient the agent to the return payload, which it does by naming the ledger contents and the `note` field for omitted metrics. Adequate for a single-parameter read tool; more detail on response shape would help but is not essential.

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?

There is a single `wallet` parameter with 100% schema description coverage, so the schema fully documents it. The description adds no format or interpretation detail about the wallet address beyond implying it identifies the agent; baseline 3 is appropriate for a one-param tool whose schema leads.

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 the specific resource (an agent's full position plus real event ledger) and enumerates what the ledger contains: stakes, unstakes, withdrawals, slashes. It also names what is excluded (WickedAPI call volume and fees) and points to the sibling that handles the lighter variant.

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?

Explicitly says when to use it (full position and ledger of stakes, unstakes, withdrawals, slashes) and when not to (quick tier check — use reputation_status). The alternative is named with the condition that selects it.

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