Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Add subsystem

add_subsystem

Create a group to organize components under a project, optionally nest it under a parent, and set its own left-to-right or top-to-bottom signal flow.

Instructions

Create a subsystem (group) to organize components, optionally nested under a parent subsystem, with its own signal flow.

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

Input Schema

NameRequiredDescriptionDefault
flowNo
nameYes
parentNo
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the agent knows this is a contained write with no destructive risk. The description adds that nesting under a parent is optional and that the new subsystem gets its own signal flow. It does not disclose what happens on duplicate names, whether a nonexistent parent fails, or what is returned.

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?

A single front-loaded sentence with no filler; the parenthetical "(group)" and the nesting clause each add meaning. Slight cost: the optional-parent detail sits mid-sentence rather than being separated for scanability.

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?

For a four-parameter creation tool with no output schema and zero schema descriptions, the definition is minimal but workable. An agent can form a valid call from it, yet would have to inspect the schema to learn that flow is LR/TB and that project_id is required and unconstrained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden. It does clarify two parameters — the subsystem name and the optional "parent" nesting — and hints at "flow" via "its own signal flow", but never ties flow to the LR/TB enum values, and project_id is entirely unaddressed.

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?

States a specific verb and resource ("Create a subsystem (group)") plus the intent ("to organize components"), which is far more than a restatement of the name. It implicitly separates itself from remove_subsystem/update_subsystem by being a creation tool, but never names a sibling or explicitly contrasts behavior.

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 only implied: you create a group to organize components, and nesting under a parent is optional. There is no statement of prerequisites (e.g. project must exist), no when-not guidance, and no routing to update_subsystem for modifications of an existing subsystem.

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