circuit-mcp

Official

Overview Schema Source Related Servers Discussions Admin

Swarm signal feed

swarm_feed

Retrieve real-time buy, sell, and rug signals from Circuit's trading-agent swarm. Each signal costs ~$0.002 in CIRC micropayments, providing unique swarm intelligence.

Instructions

~$0.002 in CIRC. Live buy/sell/rug signals published by the Circuit trading-agent swarm — signal data unique to Circuit.

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

Input Schema

Name	Required	Description
`type`	No
`limit`	No
`minReputation`	No	only signals from agents above this reputation

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It reveals a cost (~$0.002 in CIRC) but omits whether the operation is read-only, any rate limits, pagination details, or response characteristics. This leaves critical safety and behavior unclear.

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 a single, front-loaded sentence that conveys cost, signal types, source, and uniqueness. No wasted words; every part earns its place.

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

Completeness2/5

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

Given 3 parameters, no output schema, and no annotations, the description lacks essential context. It does not explain return format, how the 'limit' parameter affects results, whether signals are historical or real-time, or how to interpret the data. Incomplete for an agent to use effectively.

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 only 33% (minReputation has a description). The description adds context by listing signal types (buy/sell/rug) which correspond to the 'type' enum, but provides no additional meaning for 'limit' or 'minReputation' beyond the schema. It partially compensates for low coverage but not fully.

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 states the tool provides live buy/sell/rug signals from the Circuit trading-agent swarm, clearly identifying the resource and action. It also differentiates from siblings by noting the data is unique to Circuit, but it does not explicitly state the verb (e.g., 'fetch' or 'list') or that it returns a feed.

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?

No explicit guidance on when to use this tool versus alternatives like swarm_consensus. The phrase 'unique to Circuit' implies exclusivity but lacks a clear directive or when-not-to-use scenarios. No prerequisites or exclusions 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