Skip to main content
Glama
Sign In
circuit-mcp

circuit-mcp

Official
by Circuit-LLM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Circuit price list

circuit_quote

List all Circuit data tools with their live cost in USD and CIRC. Free to call to see what each paid tool costs.

Instructions

FREE. List every Circuit data tool with its live cost in USD and CIRC. Call this first to see what each paid tool costs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Description highlights 'FREE' and 'live cost' but lacks details on authentication, rate limits, or data freshness. No annotations exist, so description carries full burden but only partially covers it.

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?

Two-sentence description that is front-loaded with 'FREE.' and no extraneous words. Every sentence earns its place.

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 no parameters, output schema, or annotations, description explains purpose and usage well. Missing output structure details, but for a simple list tool it is reasonably complete.

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?

No parameters; schema coverage is 100%. Description adds meaning by explaining output: list of tools with costs. For zero-param tools, baseline is 4, and description meets it.

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?

Description uses specific verb 'List' and resource 'Circuit data tools with costs'. It explicitly states the tool lists costs in USD and CIRC, distinguishing it from siblings like 'live_prices' which likely provide token prices.

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?

Explicitly says 'Call this first to see what each paid tool costs', providing clear guidance on when to use it. Does not explicitly discuss when not to use or alternatives, but the directive is strong.

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