Skip to main content
Glama

mt_prediction_link

Idempotent

Link a prediction market wallet to sync Polymarket trade history, calculate a 0–100 prediction score, store the profile, and optionally attach a MolTrust DID.

Instructions

Link a prediction market wallet and sync its track record.

Fetches trade history from Polymarket, calculates a prediction score (0-100), and stores the wallet profile. Optionally links it to a MolTrust DID.

Args: address: Prediction market wallet address (0x-prefixed, 42 chars) platform: Platform name (default: "polymarket") did: Optional MolTrust DID to link (e.g. "did:moltrust:a1b2c3d4e5f60718")

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

Input Schema

NameRequiredDescriptionDefault
didNoOptional MolTrust DID to link (e.g. "did:moltrust:a1b2c3d4e5f60718")
addressYesPrediction market wallet address (0x-prefixed, 42 chars)
platformNoPlatform name (default: "polymarket")polymarket

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.1
    • addedInput schema / properties / address / description
      Added value: +"Prediction market wallet address (0x-prefixed, 42 chars)"
    • addedInput schema / properties / did / description
      Added value: +"Optional MolTrust DID to link (e.g. \"did:moltrust:a1b2c3d4e5f60718\")"
    • addedInput schema / properties / platform / description
      Added value: +"Platform name (default: \"polymarket\")"
  2. First observedv1.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. Beyond that, the description usefully discloses that this reaches out to an external system (Polymarket), persists a derived score, and can create a DID association - material behavior an agent wouldn't know from the annotations alone. It omits what happens on re-link (overwrite vs. merge) and behavior for wallets with no trade history.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded and the pipeline summary is efficient. However, the Args section duplicates information already fully present in the input schema, adding length without adding meaning for an agent that can read structured fields.

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?

An output schema exists, so return values need not be explained, and the description covers the mutation, its external data source, and the optional DID association. For a write tool with moderate complexity it is nearly complete; only edge-case behavior (invalid address, empty trade history, repeated linking) is left unstated.

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%, so the baseline is 3. The Args block restates the schema text nearly verbatim (0x-prefixed 42-char address, default platform "polymarket", DID example) without adding constraints such as supported platform values or address validation behavior.

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 first sentence names a specific verb (link) and resource (prediction market wallet) and adds a concrete outcome (sync track record). The follow-up spells out the pipeline: fetch Polymarket trade history, compute a 0-100 prediction score, store the profile, optionally attach a DID. It does not explicitly contrast with the sibling mt_prediction_wallet, so an agent must infer the boundary between linking/syncing and plain wallet lookup.

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?

The description implies usage (onboarding a Polymarket wallet into trust scoring, optionally tying it to a DID) but never states when to call this instead of mt_prediction_wallet or mt_prediction_leaderboard. No prerequisites, exclusions, or failure conditions are given, so the agent must guess at routing.

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