Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Remove subsystem

remove_subsystem
Destructive

Delete a subsystem and move its components and child subsystems to the parent or top level, preserving all other design data.

Instructions

Delete a subsystem. Nothing else is deleted: its components and child subsystems move up to its parent (or the top level).

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": {
      "project_id": "<project_id>",
      "subsystem": "<subsystem>"
    },
    "name": "remove_subsystem"
  }
}

Input Schema

NameRequiredDescriptionDefault
subsystemYesName or id
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description goes beyond that by disclosing the cascade behavior — children move up to the parent or top level rather than being destroyed — which is exactly the kind of consequence an agent cannot infer from annotations. It does not state whether the deletion is reversible, so a 4 rather than a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and immediately followed by the critical side-effect constraint. There is no filler and every clause carries information an agent needs.

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 2-parameter destructive tool with no output schema, the description covers the one non-obvious fact — what survives the deletion. Missing are the semantics of project_id scoping and any indication of the return value or irreversibility, leaving a small but real gap.

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 only 50%: 'subsystem' documents 'Name or id', but 'project_id' is bare. The description never mentions either parameter, so it does not compensate for the gap — notably it leaves ambiguous whether the subsystem is resolved globally or within project_id.

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 opens with a specific verb and resource ('Delete a subsystem') that separates it cleanly from the add_/update_ siblings. The second sentence further sharpens the scope by clarifying that child items are not deleted, which distinguishes it from remove_components and similar destructive siblings.

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?

Usage is implied rather than stated: the note that components and child subsystems survive deletion implies 'use this only to remove the container, use remove_components to remove contents.' However, no explicit when-to-use, when-not-to-use, or named alternative is given.

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