FASTMEAN MCP

Overview Schema Source Related Servers Discussions Admin

fastmean_symbolic

Generates native CIRSYM U/I/H/Z/Y formulas for supported linear zero-state circuits, deriving transfer functions from a grounded independent voltage source or output-only equations.

Instructions

Get native CIRSYM U/I/H/Z/Y formulas for supported linear zero-state circuits.

Native FASTMEAN exports connectivity before conversion to CIRSYM. Optional input must be driven by a unique grounded independent voltage source; the transfer function is derived by dividing the native output by its amplitude. Set input=null for an output equation only. Not an arbitrary equation solver.

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_symbolic"
  }
}

Input Schema

Name	Required	Default
`path`	Yes
`input`	No	in
`output`	No	out
`analysis`	No	voltage
`input_source`	No
`output_element`	No
`output_reference`	No	0

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.6.0Oct 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false. The description adds useful domain behavior about input constraints and transfer-function derivation, but it does not explain the non-read-only nature, possible export/write side effects, permissions, or what the operation produces beyond formulas.

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 purpose is front-loaded in the first sentence, and the description is dense rather than padded. Some domain-heavy sentences, such as the note about FASTMEAN exporting connectivity before CIRSYM conversion, are useful but could be structured more clearly.

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?

This is a complex 7-parameter symbolic analysis tool with no output schema and no schema parameter descriptions. The description covers the core purpose and one input constraint, but leaves most parameter meanings, return format, and side effects undocumented.

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 7 parameters, so the description must carry the burden. It clarifies the optional input and input=null behavior, but does not explain path, output, analysis enum semantics, input_source, output_element, or output_reference.

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 a specific verb and resource: 'Get native CIRSYM U/I/H/Z/Y formulas' for 'supported linear zero-state circuits.' It also explicitly excludes arbitrary equation solving, which helps distinguish it from siblings such as fastmean_evaluate or fastmean_ac.

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 gives clear prerequisites for the optional input: it must be driven by a unique grounded independent voltage source, and input=null produces an output equation only. It also states the tool is not an arbitrary equation solver, though it does not explicitly compare itself to the other simulation/analysis siblings.

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