Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Get project

get_project
Read-only

Retrieve a project's subsystems, components, P&ID items and lines, wires, and current issues; set format=json to return the raw document.

Instructions

A project's subsystems, components (tag → Codex part), P&ID items and lines, wires (grid rows) and current issues. Set format=json for the raw document.

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

Input Schema

NameRequiredDescriptionDefault
formatNotext
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value by disclosing the payload contents, including 'current issues,' which an agent would not otherwise know; however, it says nothing about error behavior for a missing project, response size, or what 'text' versus 'json' actually produces beyond 'raw document.'

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?

Two compact sentences with no padding, and the format hint is placed where it is easy to find. The opening noun fragment is slightly awkward but not wasteful.

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 simple read-only tool with annotations and no output schema, enumerating the returned data is helpful context. Still, the definition leaves the required project_id unexplained and does not characterize the two format modes, so an agent lacks a complete picture before calling it.

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 0%, so the description must carry parameter meaning. It clarifies format=json as the raw document, but never explains project_id, and leaves the default text mode and its shape undefined, so most parameter semantics remain undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase enumerating what a project contains (subsystems, components, P&ID items, wires, issues) rather than stating a verb, so the retrieval action is only implied by the name and title. It does differentiate content from siblings like list_projects or update_project, but an agent must infer that this fetches a single project's full document.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The only guidance is 'Set format=json for the raw document,' which explains a parameter choice rather than when to use this tool. There is no mention of when to prefer get_project over list_projects or export_project_file, and no prerequisites such as whether the project must exist or be validated.

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