Skip to main content
Glama

mt_prediction_wallet

Read-only

Retrieve a prediction-market wallet profile and track record, including score, win/loss, volume, ROI, score breakdown, and recent events for reputation assessment.

Instructions

Get prediction market profile and track record for a wallet.

Returns the prediction score (0-100), win/loss record, volume, ROI, score breakdown, and recent market events.

Args: address: Prediction market wallet address (0x-prefixed, 42 chars)

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": {
      "address": "<address>"
    },
    "name": "mt_prediction_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesPrediction market wallet address (0x-prefixed, 42 chars)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.1
    • addedInput schema / properties / address / description
      Added value: +"Prediction market wallet address (0x-prefixed, 42 chars)"
  2. First observedv1.2.0

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the description's main added value is the disclosure of what is returned (0-100 score, win/loss, volume, ROI, breakdown, recent events). It says nothing about behavior for unknown/invalid addresses, empty histories, or rate limits, which matters for a lookup that can plausibly return no data.

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?

Purpose is front-loaded in the first sentence with the return payload listed immediately after, which is easy to scan. The Args section duplicates the input schema verbatim and is the one piece of low-value text.

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 single-parameter read-only lookup with a full-coverage schema and an output schema, the description covers purpose and the shape of results adequately. The remaining gap is edge-case behavior for unknown wallets, which a short sentence would have closed.

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 the Args block merely repeats the schema's parameter text verbatim (0x-prefixed, 42 chars), adding no new meaning. Baseline 3 is appropriate when the schema already carries the parameter documentation.

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?

"Get prediction market profile and track record for a wallet" states a specific verb (get) and resource (wallet prediction profile), and the enumerated return fields clarify the scope. It does not, however, explicitly distinguish itself from the sibling mt_prediction_leaderboard, so an agent must infer the per-wallet vs aggregate distinction.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative such as the leaderboard sibling for ranking queries. The only signal is implicit in the noun "wallet," which the agent must interpret on its own.

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