aiseg2-mcp

list_circuits

Read-onlyIdempotent

List all registered measurement circuits and their stable IDs. Use this to get canonical circuit names from the device's installation settings, avoiding display-derived variations.

Instructions

Read-only. List the registered measurement circuits with their stable ids and names.

This is the AUTHORITATIVE source of circuit naming (from the device's installation settings).
The names in get_circuit_breakdown() are display-derived and may differ (line wraps); prefer
these when you need a canonical circuit name.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`circuits`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Adds context beyond annotations: authoritative source from installation settings, notes that names may differ due to line wraps. Annotations already cover read-only/idempotent, so description adds provenance.

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?

Three sentences, front-loaded with read-only and list action, then essential nuance. Zero 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-param tool with output schema and strong annotations, the description fully explains purpose, authoritative nature, and relationship to a sibling. 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 trivially covers everything. Baseline 4 applies.

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?

Specific verb+resource: lists registered measurement circuits with stable ids and names. Distinguishes from sibling get_circuit_breakdown by noting authoritative naming.

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?

Explicitly states when to prefer this tool (canonical circuit names) and cites get_circuit_breakdown as the alternative with display-derived names. Clear usage context.

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

Deploy Server