Skip to main content
Glama
FASTMEAN MCP

FASTMEAN MCP

by maxewka

fastmean_transient

Run native transient time-domain analysis on wire-connected schematics and return signal samples, CSV, and PNG outputs for simulation results.

Instructions

Run native time-domain analysis; return native samples, CSV and PNG.

Examples: U(out), U(in), I(R1). Seconds and SI values are numeric. Starts at time zero with the schematic's component IC values; no saved-state files. timeout limits this owned worker to 1–60 seconds (default 60).

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": {
      "path": "<path>"
    },
    "name": "fastmean_transient"
  }
}

Input Schema

NameRequiredDescriptionDefault
epsNo
pathYes
stepNo
stopNo
signalsNo
timeoutNo
overridesNo
definitionsNo
sample_afterNo
state2schemeNo
initial_conditionsNoscheme

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.0

TDQS

B3.3/5.0
Behavior4/5

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

Adds real context beyond the annotations: the simulation starts at t=0 from the schematic's component IC values, saved-state files are not consulted, the run occupies an 'owned worker', and timeout is clamped to 1–60s with a 60s default. That worker-ownership and timeout detail is exactly the kind of operational trait annotations (readOnly/destructive hints) do not convey.

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?

Front-loaded with the purpose and return artifacts, then operational constraints. The examples line is useful; a little more could be trimmed, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter simulation tool with no output schema and zero schema descriptions, the definition leaves most parameters opaque and gives no picture of the result structure beyond naming the three output artifacts. The behavioral hints are good; the parameter coverage is not.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 11 parameters, so the description must compensate and largely does not. It gives signal-expression syntax (U(out), I(R1)) and numeric/SI units, plus timeout semantics, but says nothing about step, stop, eps, sample_after, overrides, definitions, state2scheme, initial_conditions (only obliquely via 'component IC values'), or path.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Run native time-domain analysis' with the outputs enumerated (native samples, CSV, PNG). 'Time-domain' implicitly separates it from the frequency-domain siblings (fastmean_ac, fastmean_spectrum) and fastmean_dc, though it never names them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not-to-use statement; the agent must infer the choice between this and fastmean_ac / fastmean_dc / fastmean_sweep from domain knowledge. 'No saved-state files' is the only exclusion given, and it is a constraint rather than a routing rule.

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