FASTMEAN MCP

Overview Schema Source Related Servers Discussions Admin

fastmean_open

Opens a FASTMEAN working copy through the installed executable's CLI, packages SCM model dependencies, records source/copy hashes, and leaves existing windows untouched.

Instructions

Open a working copy through the installed FASTMEAN executable's documented CLI.

Recursively packages SCM model dependencies and records source/copy hashes. Starts a separate application process; leaves existing windows alone. The circuit window stays open for the user, and is not controlled automatically. This command does not apply locale emulation; old Russian UI text may appear garbled on Windows configured for another legacy code page.

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

Input Schema

Name	Required	Description	Default
`path`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.6.0Oct 29, 2026

TDQS

A3.6/5.0

Behavior5/5

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

Beyond the annotations, the description discloses meaningful behavior: recursive dependency packaging, source/copy hash recording, separate process startup, non-interference with existing windows, the circuit window remaining open and uncontrolled, and a locale/legacy-codepage caveat. These details are consistent with the non-read-only, non-destructive, non-idempotent, non-open-world 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 description is front-loaded with purpose and then adds side effects, process behavior, and operational caveats in a logical order. It is reasonably tight, though the locale sentence is lengthy and some phrasing could be tightened without losing meaning.

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

Completeness3/5

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

Because an output schema exists, return values need not be explained, and the annotations cover safety characteristics. The description is strong on process and window behavior, but the critical `path` input remains undefined and there is no sibling routing guidance, leaving a notable gap for correct invocation.

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?

The sole required parameter is `path`, and schema description coverage is 0%. The description never explains what `path` should point to, whether it is a model file, project file, directory, or working-copy path, nor does it describe accepted formats or resolution rules.

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 first sentence provides a specific verb and resource: 'Open a working copy' via the installed FASTMEAN executable's CLI. It is clear what the tool does, but it does not contrast itself with siblings such as fastmean_preview or fastmean_create_circuit, so it falls short of full sibling differentiation.

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?

The description gives behavioral context that implies when the tool is appropriate, such as starting a separate process and leaving existing windows alone. However, it does not explicitly state when to use this tool instead of alternatives, nor does it provide prerequisites or exclusions.

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