Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

List P&ID symbols

list_pid_symbols
Read-only

List P&ID symbol definitions by group, including labels, base sizes, resize behavior, and port offsets, to select symbols and place ports accurately in schematics.

Instructions

P&ID symbols by group: key, label, base size, whether it resizes, and its ports with their x,y offset from the item's centre at that size. A resized item's ports are listed when it is added.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_pid_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description instead adds payload semantics the agent could not otherwise know — port coordinates are x,y offsets from the item's centre at the base size, and resized items carry their own port list. It does not say whether the catalog is static, grouped, or paginated, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no padding, and the useful geometry caveat is placed second where it reads as an afterthought. The opening is a noun phrase rather than a sentence, so the core action is never front-loaded, which costs a point despite the compact size.

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?

There is no output schema, so the field enumeration ('key, label, base size, whether it resizes, ports') is doing necessary work and is the strongest part of the definition. What remains unclear is scope: whether all groups are returned, whether symbols are nested under groups, and how 'key' relates to the arguments of add_pid_items.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter information is missing or misleading.

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 fragment 'P&ID symbols by group' implies a listing of symbol definitions, and the enumerated fields make the resource concrete. However, no verb is ever stated ('list', 'return', 'enumerate'), so the agent must infer the action from the name and title. It does not explicitly distinguish itself from siblings such as add_pid_items or list_signal_types.

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?

There is no when-to-use guidance, no prerequisites, and no mention of an alternative tool or workflow. The clause 'A resized item's ports are listed when it is added' hints at a relationship with the add flow, but it never tells the agent to call this tool before add_pid_items or to look up keys before mutating.

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