circuitarium-mcp

Overview Schema Source Related Servers Discussions Admin

Orient to Circuitarium MCP

electronics_capabilities

Read-onlyIdempotent

Learn the server's model-neutral conventions, callable backends, truthful limitations, and recommended workflows. Call this first when unsure.

Instructions

Zero-argument onboarding for model-neutral conventions, callable backends, truthful limitations, and recommended workflows. Call this first when unsure.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No
`context`	Yes
`summary`	Yes
`diagnostics`	Yes
`nextActions`	Yes
`contractVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Jul 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds valuable context by mentioning 'truthful limitations' and 'recommended workflows.' This goes beyond the annotations and reassures that the tool provides honest constraints and guidance. No contradiction with annotations.

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, well-structured sentence that front-loads the key fact ('Zero-argument onboarding') and then lists contents. It is efficient with no wasted words.

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 onboarding tool with an output schema, the description covers the essential content areas (conventions, backends, limitations, workflows). It fully describes the tool's scope without needing to document parameters or return values, and the output schema covers specific return structure.

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 for parameter semantics is 4. The description reinforces that it's zero-argument but adds no additional parameter meaning, which is unnecessary given no parameters exist.

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 is for orientation/onboarding to Circuitarium MCP, listing specific content areas (conventions, backends, limitations, workflows). It uses a specific verb ('orient') and is distinguishable from sibling tools which perform specific design/logic operations rather than meta-level overview.

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?

Explicit guidance is given: 'Call this first when unsure.' This establishes when to use the tool and implies that if you know what you're doing, you can skip it. It also clarifies that it's a zero-argument first step, which is direct and actionable.

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