Skip to main content
Glama
Sign In

Polyrank

by io.github.polyrank
OverviewDiscussionsAdmin

Polyrank trader calibration (by masked id)

polyrank_get_trader_calibration_by_tid
Read-onlyIdempotent

A trader’s 10-bin reliability diagram (predicted probability vs observed outcome rate) keyed by the opaque masked id (tid) from a leaderboard / pulse / movers / top-ROI row. Calibration is the core skill signal — whether the trader’s probabilities match reality. Completes the discovery → tid → calibration loop without needing the raw wallet. Returns bins + total resolved count.

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": {
      "tid": "<tid>"
    },
    "name": "polyrank_get_trader_calibration_by_tid"
  }
}

Input Schema

NameRequiredDescriptionDefault
tidYesOpaque trader id (tid) from a masked row.

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 declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds value beyond them by disclosing the return payload ('bins + total resolved count') and the notable fact that no raw wallet is required, though it says nothing about behaviour for traders with few resolved markets or invalid tids.

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?

Three sentences, front-loaded with the definition of the returned artifact before the keying mechanism and the workflow framing. The clause 'Calibration is the core skill signal — whether the trader's probabilities match reality' is slightly rhetorical but does real work by justifying why an agent should prefer this over other signals.

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 no output schema, the description covers what it returns, where the input comes from, and how it fits a multi-step workflow. Remaining gaps (degenerate/empty bins, invalid-tid errors) are minor for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and there is only one parameter, so the baseline would be 3. The description earns a point by expanding on where the tid originates (leaderboard / pulse / movers / top-ROI rows) and emphasizing that it is opaque and masked, which tells the agent not to attempt address-format validation.

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 a specific verb and resource — a 10-bin reliability diagram of predicted probability vs observed outcome rate — and keys it to the opaque masked tid rather than a raw wallet, which is what separates it from the wallet-based calibration and metrics siblings. The parenthetical gloss makes the domain term ('calibration') unambiguous for an agent that has never seen the term.

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

Usage Guidelines4/5

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

Gives concrete provenance for the required input by naming the row types (leaderboard / pulse / movers / top-ROI) where a tid can be obtained, and frames the tool as the final step of a 'discovery → tid → calibration' workflow. It stops short of naming an alternative tool (e.g. the raw-wallet calibration variant or the tid resolver) or stating when not to use it.

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

All Polyrank 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