FASTMEAN MCP

by maxewka

Overview Schema Source Related Servers Discussions Admin

Python

Local

fastmean_cancel

Cancels one active native operation by operation ID without affecting other processes.

Instructions

Cancel one active native operation listed by status; never other processes.

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": {
      "operation_id": "<operation_id>"
    },
    "name": "fastmean_cancel"
  }
}

Input Schema

Name	Required	Description	Default
`operation_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.6.0Oct 29, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already say readOnlyHint=false and destructiveHint=false; the description adds that only active native operations are affected and other processes are excluded. However, it does not disclose whether cancellation is reversible, what happens to outputs/results, or permission/error behavior.

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?

One front-loaded sentence with no repetition is appropriate for a one-parameter tool. The phrase 'listed by status' is terse to the point of ambiguity, but the structure is efficient.

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?

Output schema exists, so return values need not be described, and annotations cover basic safety. Still, for a cancellation mutation the definition omits how to obtain the operation ID, valid statuses, and post-cancel effects.

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 schema gives only operation_id as a string with no description, and the description does not explain its format. It does add that the identifier must refer to an active native operation listed by status, but that is minimal compensation for 0% schema coverage.

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 gives a specific verb ('Cancel') and resource ('one active native operation') and scopes it against other processes. It stops short of naming the sibling status tool or clarifying what 'native operation' covers, so it is clear but not fully differentiated.

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?

It implies the operation_id should come from a status listing and explicitly excludes other processes, which gives minimal usage context. It does not explicitly say to call fastmean_status first or state when cancellation is inappropriate.

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