aiseg2-mcp

get_circuit_breakdown

Read-onlyIdempotent

Retrieve real-time power draw for every circuit, ranked highest first, including total watts and device page count.

Instructions

Read-only. Get the instantaneous power draw of every measured circuit, ranked highest first.

Pages through the AiSEG2's circuit list and returns each circuit's rank, name and watts, plus
the total measured watts and how many device pages were read. Circuit names here are
display-derived (they may wrap); list_circuits() is the authoritative name source.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`circuits`	Yes
`page_count`	Yes
`total_watt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive. The description adds behavioral detail beyond annotations: it pages through the AiSEG2's circuit list, returns ranks, names, watts, total watts, and page count, and warns that names may wrap. This is useful context not present in structured fields.

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 the core purpose, followed by paging behavior and a name caveat. Every sentence earns its place; no redundancy or fluff.

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?

Given the tool has no parameters and an output schema exists, the description covers the necessary context: what it does, how it pages, what it returns, and a name accuracy caveat. This is complete for an agent to select and invoke the tool correctly.

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?

With zero parameters, the baseline is 4. The description does not need to explain parameters; instead it clarifies what the output contains (rank, name, watts, total, pages), providing semantic value beyond the empty schema.

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 states the tool 'Get[s] the instantaneous power draw of every measured circuit, ranked highest first,' which is a specific verb+resource+scope. It distinguishes from the sibling list_circuits by noting that names here are display-derived and list_circuits is authoritative.

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?

Provides clear context that this is for measuring instantaneous power per circuit and explicitly says list_circuits() is the authoritative name source, guiding when to use the alternative. It does not explicitly enumerate all exclusions but gives practical guidance.

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

Deploy Server