Skip to main content
Glama
Sign In

MolTrust MCP Server

by io.github.MoltyCel
OverviewDiscussionsAdmin

mt_prediction_link

Idempotent

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")

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 changed
    • 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 observed

TDQS

A3.5/5.0
Behavior4/5

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

Beyond annotations, the description explains the operational flow: fetching trade history from Polymarket, calculating a 0-100 prediction score, storing the wallet profile, and optionally linking a MolTrust DID. It does not mention permission requirements or rate limits, but it provides substantive context about what happens during the call.

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?

The description is front-loaded with the main action and flow, then lists arguments. The Args section duplicates the schema almost verbatim, which is slightly redundant, but the overall size and structure remain efficient.

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?

The tool is a mutating operation with an output schema and annotations, and the description adequately explains the fetch-calculate-store-link flow. It does not cover edge cases such as re-linking an existing wallet, but it is complete enough for correct invocation.

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 schema already documents all three parameters. The Args section repeats the same information without adding format, constraints, or meaning beyond the schema, so the baseline score of 3 applies.

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 description clearly states the specific verb and resource: linking a prediction market wallet and syncing its track record, with additional detail about fetching trade history, calculating a score, and storing a wallet profile. It does not explicitly distinguish this from the sibling mt_prediction_wallet, so sibling differentiation is left implicit.

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?

The description describes what the tool does but gives no explicit guidance on when to use it versus alternatives such as mt_prediction_wallet or mt_prediction_leaderboard. Usage is only implied by the action of linking and syncing.

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

All MolTrust MCP Server 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