Skip to main content
Glama
Sign In
FASTMEAN MCP

FASTMEAN MCP

by maxewka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fastmean_example

Read-onlyIdempotent

Generate editable JSON specs for RC/RLC low-pass filters, voltage dividers, and flyback converters, including components and voltage waveforms for simulation.

Instructions

Get an editable JSON spec: rc_lowpass, rlc_lowpass, voltage_divider, flyback.

components have kind, name, nodes [positive,negative] for U/V, and SI value. Voltage waveform: {kind:dc|sine|pulse, frequency, amplitude, phase, delay, high, low, duty_percent, rise_time}; only fields applicable to its kind. flyback uses a native TR transformer, separate magnetizing L, native SW voltage-controlled switch, pulse drive and diode rectifier. Use transient.

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

Input Schema

NameRequiredDescriptionDefault
kindNorc_lowpass

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false. The description adds useful behavioral context beyond that: the result is an editable JSON spec, components use kind/name/nodes/value, and flyback requires a native TR transformer and transient analysis. No annotation contradiction is present.

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 description is front-loaded with the main purpose and valid example list, then moves into compact schema notes. Some return-structure details may duplicate the output schema, but there is no obvious filler and the structure is clear.

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 one-optional-parameter read-only example tool with an output schema, the description supplies the missing valid kind values and important flyback simulation context. It stops short of linking the returned spec back to create/edit tools, so it is not fully complete.

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?

The schema has 0% description coverage and no enum, so the description must compensate. It does so by listing the valid values rc_lowpass, rlc_lowpass, voltage_divider, and flyback, and by giving flyback-specific semantics, though it does not explicitly name the kind parameter or explain each circuit type.

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?

The description opens with a specific verb and resource ("Get an editable JSON spec") and enumerates the four example circuit kinds. It does not explicitly differentiate this tool from siblings such as fastmean_list_examples or fastmean_catalog, so it falls short of a 5.

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

Usage Guidelines2/5

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

The only usage instruction is "Use transient" for flyback, which applies to simulating the returned circuit rather than selecting this tool. It never says when to use fastmean_example instead of fastmean_list_examples or fastmean_catalog, nor how the editable spec should be used afterward.

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

Deploy Server

Other Tools