Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Create project

create_project

Start a new wiring schematic project, optionally from the Arduino Parking Sensor sample or inside a team/class workspace with private-to-team access.

Instructions

Create a new project (Free plan: max 3, always public). sample=true starts from the sample project (the Arduino Parking Sensor template). Pass team (name or id) to create it in a team or class: it starts private to you and the team's owner/admins; share it from Ohmstead.

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": {
      "title": "<title>"
    },
    "name": "create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoTeam or class name or id (you must be an editor/student or up). Omit for your personal workspace.
titleYes
sampleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare a non-destructive, non-open write, and the description adds real context beyond them: the free-plan cap of 3, forced public visibility, template-based creation, and the privacy default when creating in a team (visible to you plus owner/admins, shared from Ohmstead). It stops short of saying what is returned (e.g. a project id) or what happens when the plan limit is hit.

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?

Three dense sentences with the core action and plan constraint front-loaded, then the two optional parameters. The parentheticals ("the Arduino Parking Sensor template", "name or id") earn their place, though the closing "share it from Ohmstead" reads as an aside that slightly interrupts flow.

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 3-parameter mutation with no output schema and thin schema coverage, the description covers limits, visibility defaults, and both optional flags. The main remaining gap is the return value (an id an agent would need for follow-up calls), which no structured field supplies.

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 description coverage is only 33%, so the description must compensate, and it does for both non-trivial params: sample=true is explained as the specific Arduino Parking Sensor template, and team is clarified as "name or id" with privacy consequences. title gets no explanation but is self-evident from the required field.

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 verb and resource ("Create a new project") and immediately scopes it with plan limits ("Free plan: max 3, always public"), which no sibling (list_projects, get_project, update_project) does. An agent can distinguish this from the read/update project tools on the verb alone.

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 clear conditions for the two optional behaviors: use sample=true to start from the Arduino Parking Sensor template, and pass team to create inside a team or class. It does not explicitly exclude alternatives (e.g. "use update_project to modify an existing one"), but the creation-only framing is unambiguous.

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