Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Search Codex

search_codex
Read-only

Find components in the Ohmstead parts library by name, part number, manufacturer, description, or terminal name across built-in, community, and personal listings.

Instructions

Search the parts library (built-in, community and yours) by name, part number, manufacturer, description or terminal name.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
categoryNoOne of: device, plc, psu, battery, relay, terminal, estop, io, hmi, breaker, motor, sensor, resistor, capacitor, inductor, diode
mine_onlyNo
manufacturerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/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 the safety profile is covered. The description adds genuinely useful scope information, namely that the corpus spans built-in, community, and personal libraries. It still omits behavior an agent would want: what happens with the default empty query (does it list everything?), how results are ordered, and how the limit interacts with pagination.

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?

A single front-loaded sentence that states the action, the corpus scope, and the matchable fields with zero filler. Nothing is repeated from the schema and no phrase is redundant.

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 read-only search with no output schema and five parameters at 20% description coverage, the definition covers purpose but leaves meaningful gaps. An agent cannot tell from the definition whether an empty query enumerates the library, what shape results take, or how to page through more than the default 20 matches.

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?

Schema description coverage is only 20%, so the description must carry weight, and it partly does by explaining which fields the free-text query matches and by mentioning manufacturer, which is also a separate parameter. It says nothing about limit, mine_only, or how query interacts with the category filter, leaving three of five parameters undocumented anywhere.

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 concrete verb (search) and a concrete resource (the parts library), and enumerates the searchable fields: name, part number, manufacturer, description, terminal name. It also scopes the corpus to built-in, community, and the user's own parts. It stops short of naming a sibling like list_manufacturers as an alternative, so a 4 rather than 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 Guidelines2/5

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

There is no explicit when-to-use guidance, no statement of when another tool is preferable (e.g. list_manufacturers for enumerating vendors, add_components for the follow-up action), and no prerequisites. The appropriate usage of a library search is only implied by the verb 'search'.

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