Skip to main content
Glama
Sign In
orcatrace-mcp

orcatrace-mcp

by jcislo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_sample

Explore free, labeled Polymarket response samples (signals, whales, digests) to learn the data shapes before paying. No API key needed; 5 requests per minute per IP.

Instructions

Static samples of every paid Polymarket response shape (signal, whales, digest), explicitly labelled — use it to learn the contract before paying (GET /v1/sample). FREE, rate-limited 5/min per IP, no wallet or API key required.

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

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 provided, the description fully discloses key behaviors: it is FREE, rate-limited to 5/min per IP, requires no wallet or API key, and returns static labelled samples rather than live data. This goes beyond typical descriptions.

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?

A single, information-dense sentence covers purpose, usage, cost, rate limit, auth, and static nature. Every element earns its place without waste.

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?

For a zero-parameter tool with no output schema, the description is complete: it explains what the sample is, why someone would use it, and all constraints. No gaps remain.

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?

The tool has zero parameters, so the baseline is 4. The description adds no parameter details but also doesn't need to; the empty schema is self-explanatory.

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 tool provides 'Static samples of every paid Polymarket response shape' and lists specific shapes (signal, whales, digest). This distinguishes it from sibling tools that return actual data or other types of information.

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?

The description explicitly says to 'use it to learn the contract before paying', giving clear when-to-use guidance. It also differentiates from paid alternatives by being FREE and sample-only.

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