Skip to main content
Glama
Sign In
orcatrace-mcp

orcatrace-mcp

by jcislo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_digest

Get a synthesized Polymarket intelligence digest every 4 hours, covering significant repricings, whale positioning, and news context across 42K markets.

Instructions

PAID $0.10 via x402. The full Polymarket Intelligence Digest (generated every 4h): what repriced and why across 42K markets — significant moves, whale positioning read through calibration, predetermined-outcome signals, and international news context. Synthesized analysis, not raw data. Never serves stale (returns 503, no charge, if generation falls behind). Free teaser: get_digest_brief. Pays USDC on Base via x402. Compute-first / settle-after — you are never charged for an error. Set PRIVATE_KEY (wallet with USDC on Base Mainnet) to pay on a live API; without a key the call returns the 402 price terms.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: paid ($0.10), compute-first/settle-after (never charged for errors), freshness policy (never serves stale, returns 503 if behind), and returns 402 without a key. This is exemplary transparency.

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

Conciseness5/5

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

Every sentence adds critical value: payment, content, analysis type, freshness, free alternative, payment mechanics, and key requirement. It is dense but well-structured, front-loading the payment requirement and delivering comprehensive information without fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description thoroughly covers the operational aspects: what the digest contains, when it's generated, how payment works, error statuses (503, 402), and the free alternative. It is complete and leaves no critical gaps.

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?

There are no parameters in the schema (0 params), so the baseline per rubric is 4. The description appropriately adds context about the PRIVATE_KEY environment variable, which is not a parameter but is essential for usage, without cluttering parameter semantics.

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 it provides the full Polymarket Intelligence Digest, generated every 4 hours, and details what it contains (significant moves, whale positioning, news context). It distinguishes itself from the sibling get_digest_brief by describing the latter as a free teaser.

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

Usage Guidelines5/5

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

Explicitly names get_digest_brief as a free alternative, and provides clear usage conditions: payment via x402, PRIVATE_KEY requirement, and the 402 price terms when no key is set. This tells the agent when to use this tool versus alternatives.

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

Deploy Server

Other Tools