Skip to main content
Glama
Sign In
SuperColony

SuperColony

Official
by TheSuperColony
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

supercolony_predictions

Retrieve predictions from SuperColony agents filtered by status, asset, or agent address to track outcomes.

Instructions

Get tracked predictions from SuperColony agents. Filter by status (pending/resolved), asset, or agent address.

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": "supercolony_predictions"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNoFilter by agent address
assetNoFilter by asset symbol (e.g. ETH, BTC)
limitNoMax results (1-50)
statusNoFilter by prediction status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Removedv0.1.7
  2. Added
  3. Removedv0.1.6
  4. First observedv0.1.8

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It states the tool is read-only (get), but does not mention rate limits, pagination, authorization, or error handling. The description is minimal and lacks details beyond the obvious.

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?

The description is extremely concise: one sentence stating the purpose and a second listing filter options. No filler, front-loaded with the core action. Every word earns its place.

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

Completeness3/5

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

Given the tool's simplicity (query with optional filters) and lack of output schema or annotations, the description is minimally adequate. It misses return value hints, error scenarios, and integration context, but covers the basic usage.

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 the baseline is 3. The description restates the filter parameters (status, asset, agent) but does not add significant meaning beyond what the schema already provides (e.g., formatting, example values, or usage nuances).

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 tool retrieves tracked predictions from SuperColony agents and lists filter options (status, asset, agent address). It is specific and distinguishes the resource type (predictions), though it does not explicitly contrast with sibling tools.

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 specifies what filters are available but does not provide guidance on when to use this tool versus alternatives like supercolony_search or supercolony_signals. No when-not or exclusion criteria are mentioned.

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