Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Export project file

export_project_file
Read-only

Export an Ohmstead project as a plain-text .ohmstead file so you can commit it to Git, edit it, and re-import changes.

Instructions

The project as an Ohmstead project file (.ohmstead): plain text, one line per part and wire, sorted, addressed by tag, with drag positions and draw order in the last section. Commit it to Git or edit it and bring it back with import_project_file. Lines starting with # at the top list references that were left out because what they point at no longer exists.

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": "export_project_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes

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?

Beyond the readOnly/openWorld annotations, it discloses the actual output shape: plain text, one line per part and wire, sorted, addressed by tag, drag positions and draw order in a trailing section. Crucially it warns that lines starting with # at the top list references omitted because their targets no longer exist, which is real behavioral information an agent cannot get from the annotations or schema.

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 passage that opens with the artifact and its format, then the round-trip alternative, then the caveat about omitted references. Dense but every clause carries information; only minor trimming is possible.

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?

With no output schema, the description carries the return-value burden and does so thoroughly, covering format, ordering, and the header comment section. The only meaningful gap for a one-parameter tool is the unspecified project_id format.

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?

The single project_id parameter has 0% schema description coverage, and the description only implies it via 'The project' without stating accepted format (ID vs name) or error behavior for unknown projects. It adds partial meaning but does not fully compensate for the undocumented parameter.

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?

States a specific action and resource: the project serialized as a .ohmstead file, and immediately contrasts it with the sibling import_project_file. An agent can distinguish export from import and from get_project without opening the schema.

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?

Gives concrete usage contexts ('Commit it to Git or edit it and bring it back') and names the round-trip sibling import_project_file. It stops short of explicit exclusions (e.g., when to use get_project instead for programmatic access), but the intended workflow is clear.

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