Skip to main content
Glama

simulate

Read-only

Compute a circuit's or sheet's DC operating point by setting nets to voltages, closing switches, and energizing relay coils; run a sheet's predefined cases when no set values are provided.

Instructions

DC operating point of a circuit, or of a sheet beside it: set nets to volts ("open" floats), close switches, energise relay coils; answers nets, sources, parts beyond a limit, then each part. With sheet and no set it runs the sheet's cases; no time, frequency or tolerance, and chips are not modelled.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file": "<file>"
    },
    "name": "simulate"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNo
setNoe.g. { "V12": 12, "GND": 0, "CTRL": 3.3 }
coilNo
fileYes
sheetNo
closedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare this read-only and non-destructive, and the description adds substantial scope details: simulation-only behaviour, the 'open' floating-net sentinel, switch/coil controls, sheet-case execution, and model limitations. The return description is somewhat terse but still adds meaningful behavioural context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is dense and front-loads the purpose, then moves through inputs, output categories, conditional sheet behaviour, and limitations with no filler. Some phrasing, especially 'parts beyond a limit, then each part', is compressed enough to be slightly cryptic.

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?

For a simulation tool with no output schema and low input-schema coverage, the description provides most of the operational context an agent needs: scope, controls, sheet mode, and hard limits. It is still incomplete because the all parameter and exact return structure are not fully explained.

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 only 17% schema description coverage, the description compensates well by explaining the meanings of set, closed, coil, and sheet, including that set values are volts and that "open" floats a net. It leaves the all and file parameters unexplained, so the compensation is strong but not complete.

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 names the exact analysis: a DC operating point of a circuit or a nearby sheet. That is a specific verb-and-resource scope, and the stated DC-only limitation helps distinguish it from transient or frequency-domain analyses.

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?

It clearly indicates when the tool applies: DC operating point, optional sheet execution when no set is supplied, and explicit exclusions for time, frequency, tolerance, and chip modelling. It stops short of naming alternative tools for those excluded analyses.

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