FASTMEAN MCP

Overview Schema Source Related Servers Discussions Admin

fastmean_edit_values

Edit component values in a copied schematic by mapping names to SI values or waveform settings while retaining topology and native objects; the source file stays unchanged.

Instructions

Create an edited copy, retaining topology and unknown native objects.

updates maps component names to SI values, or to {value:...,waveform:...}. This supports R/C/L/U/I value edits and never overwrites the selected source. A literal edit replaces any parameter binding on that component. To keep shared .parameter bindings, use fastmean_edit_parameters instead. Explicit waveform fields update the selected mode, retaining omitted fields and other modes; waveform amplitude/high overrides value when supplied.

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>",
      "updates": "<updates>"
    },
    "name": "fastmean_edit_values"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`updates`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.6.0Oct 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare non-readonly, non-destructive, non-idempotent, but the description goes well beyond them: 'never overwrites the selected source', retains topology and unknown native objects, and that a literal edit replaces parameter bindings. It also specifies precedence (amplitude/high overrides value) and mode-retention behavior — genuinely useful mutation context.

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 core behavior ('edited copy, retaining topology') is front-loaded, and the dense detail that follows all earns its place by clarifying update semantics. The mid-paragraph pivot to .parameter bindings is slightly run-on but not wasteful.

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?

With an output schema present, return values needn't be described, and the description fills the nested-object ambiguity around `updates` well. It is complete enough to call correctly, missing only an explicit note on what `path` denotes.

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?

Schema coverage is 0%, so the description must carry the load, and it thoroughly documents the complex `updates` param: component-name→SI value, or {value, waveform}, waveform field semantics, and override precedence. The `path` parameter is left entirely unexplained (though its purpose is inferable as the source circuit), which is the only notable gap.

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 opening sentence gives a specific verb and resource: 'Create an edited copy, retaining topology and unknown native objects.' Combined with 'updates maps component names to SI values' and the explicit pointer to fastmean_edit_parameters, an agent can immediately tell this apart from its closest sibling without opening either schema.

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?

The description gives a concrete when-to-use-elsewhere rule: 'To keep shared .parameter bindings, use fastmean_edit_parameters instead.' It also states what this tool does to bindings ('A literal edit replaces any parameter binding'), so the tradeoff is explicit. It does not discuss other siblings like fastmean_edit_properties, but the key alternative and condition are covered.

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