Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Import project file

import_project_file

Preview and import Ohmstead project files: report changes first, then apply them to an existing project or create a new one while preserving component and wire IDs.

Instructions

Read an Ohmstead project file (.ohmstead text). With project_id it goes over that project: components, subsystems and wires keep their ids by tag, so saved positions and embeds survive. Without apply it only reports what would change (always do that first and show the user); apply=true saves. Without project_id it makes a new project named title (Free plan: max 3). Parts resolve by id, then by maker and number; anything missing or ambiguous is named and nothing is saved.

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": {
      "text": "<text>"
    },
    "name": "import_project_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoTeam or class for a new project. Omit for your personal workspace.
textYes
applyNo
titleNoName for a new project (without project_id).
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnly=false, destructive=false, openWorld=false); the description adds real behavioral detail beyond that: dry-run by default, what apply=true commits, that ids are preserved by tag so positions and embeds survive, the Free-plan cap of 3 projects, and the part-resolution order (id, then maker and number). It also discloses the failure mode: missing or ambiguous parts are named and nothing is saved.

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?

Four sentences, each carrying unique information: format, the project_id branch, the dry-run/apply contract, and the no-project_id branch with plan limits and resolution/error behavior. The two-mode structure is front-loaded and nothing is repeated from the schema or annotations.

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 5-parameter mutation tool with no output schema, the description covers the important unknowns: default dry-run behavior, what saving does, quota limits, and error handling on unresolvable parts. The only omission is what the dry-run report actually looks like, which would help an agent present results to the user.

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?

Schema coverage is only 40% and text, project_id and apply have no schema descriptions, so the description must compensate — and it does, explaining that text is the .ohmstead content, project_id selects the target project, and apply toggles save versus report. title and team are covered by the schema itself. The only small gap is that the team parameter's effect on a new project's ownership is left entirely to the schema.

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 names a specific verb and resource ('Read an Ohmstead project file (.ohmstead text)') and clearly separates its two modes: overwrite/update an existing project via project_id versus creating a new one via title. The file-format specificity implicitly separates it from import_wiring_list, but no sibling is named explicitly, which keeps it just 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 Guidelines4/5

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

It gives strong procedural guidance: 'Without apply it only reports what would change (always do that first and show the user); apply=true saves.' That is an explicit when-to-use rule with a recommended sequence. It does not name an alternative tool or state when-not to use this one, so it stops at 4.

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