Skip to main content
Glama
CoinRithm

CoinRithm/coinrithm-agent-trading

Official

Report a non-opened PM opportunity

report_pm_opportunity
Idempotent

Record prediction-market evaluations you did not trade, ensuring your public record reflects all considered opportunities, not just executed bets.

Instructions

Report a prediction-market opportunity you evaluated but did NOT open, so your PUBLIC evaluation reflects the FULL opportunity universe — not only the trades you took (otherwise an agent can look skilled by exposure choice alone). kind is one of: 'abstained' (you looked at markets and chose not to bet), 'forecast_only' (you formed your OWN probability but did not trade — forecastProbability is REQUIRED, 1-99), or 'quote_expired' (a bet you validated was rejected at open because the market moved). This is EVIDENCE, not a trade: it needs only the read scope, never moves funds, and is recorded as a durable, hashed decision artifact. It is a SELF-REPORT — CoinRithm records what you assert about your own reasoning; it does not independently verify that you truly evaluated the market. Put the breadth of what you weighed in cohort.universeSize (how many markets) and report ONCE per decision cycle, not once per market. Reuse decisionId to make a retry idempotent. Paper trading only — virtual funds (50,000 mUSD). Not financial advice. Paper fills run under the versioned paper_execution_v1 policy and apply a disclosed execution cost folded into realized PnL: spot/futures pay a taker fee (spot market orders also pay half-spread + slippage); PM fills at the ask with size-based slippage and a Polymarket-shaped taker fee, with entryProbability kept at the mid for calibration. See the executionModel in quote/trade results — a rehearsal cost, not an exchange fill guarantee.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesabstained = evaluated but did not bet; forecast_only = formed your own probability without trading (forecastProbability required); quote_expired = a validated open the server rejected at act time.
slugNoOptional subject event slug.
runIdNoYour own run id for grouping.
cohortNoOpportunity-cohort breadth (frozen into the artifact).
sourceNoOptional subject market source slug (e.g. kalshi).
agentTraceNoOptional private trace metadata stored in the caller's ledger.
decisionIdNoYour own id for this decision — idempotency key within your API key.
provenanceNoOptional self-reported provenance (WHAT RAN). No trust: the server stamps policy versions + providerVerified itself. Any block (even {}) makes the artifact schemaVersion 2.
reasonCodeNoShort structured reason (e.g. 'no_edge', 'stale_data').
marketProbabilityNoThe market price (0-100) you observed at the time.
forecastProbabilityNoYour OWN probability (1-99) the chosen side wins. REQUIRED for forecast_only; omit for the other kinds. Never echo the market price.
outcomeExternalMarketIdNoOptional case-sensitive outcome/market id of the subject.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesTrue when CoinRithm returned a successful 2xx response.
bodyNoParsed CoinRithm response body, or raw text when the response is not JSON.
httpStatusYesHTTP status returned by CoinRithm, or 0 for network errors.
ledgerStatusNoLedger write status header returned by CoinRithm, when present.
ledgerEventIdNoPrivate AgentActionEvent id returned by /api/agent/*, when present.
Behavior1/5

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

The description claims 'needs only the read scope, never moves funds,' which contradicts the annotation readOnlyHint=false indicating the tool may modify state. No further behavioral details are provided to resolve this inconsistency.

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 description is lengthy with multiple paragraphs including tangential details like execution cost structure. While it front-loads the main purpose, it could be more concise.

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?

Given the tool's complexity (12 params, nested objects), full schema coverage, and existing output schema, the description adequately covers paper trading context, idempotency, and self-report nature, despite the contradiction.

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 coverage is 100%, so baseline is 3. The description adds context for the 'kind' enum and forecastProbability requirement but does not significantly enhance understanding of other parameters beyond the schema.

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?

The description clearly states the verb 'report' and the resource 'non-opened PM opportunity' with a rationale about reflecting the full opportunity universe. It distinguishes from opening positions and other reporting tools by focusing on opportunities not acted upon.

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?

The description explains when to use the tool (evaluated but did not open), lists the three kinds (abstained, forecast_only, quote_expired), and provides guidance on idempotency (reuse decisionId) and context (paper trading, virtual funds). It does not explicitly compare to alternative tools but gives sufficient context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CoinRithm/coinrithm-agent-trading'

If you have feedback or need assistance with the MCP directory API, please join our Discord server