Skip to main content
Glama
formastep-mcp
by eldertek

step_inspect

Read-onlyIdempotent

Inspect and validate an ISO 10303-21 STEP (.step/.stp) file to check its structure and integrity before downstream manufacturing use.

Instructions

Inspect and validate an ISO 10303-21 STEP (.step/.stp) file.

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": {
      "file_path": "<file_path>"
    },
    "name": "step_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without prose. The description adds only that the operation is a validation of a specific file format; it does not say whether validation failures surface as errors or as returned findings, or what depth of inspection occurs, which is the remaining meaningful gap.

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?

A single front-loaded sentence with zero wasted words, and the file-format constraint is stated immediately. The terseness borders on under-specification rather than excess, so it is efficient but thin.

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?

Because an output schema exists, return-value description is not required, and the read-only annotations cover behavior. What remains missing is what "inspect" versus "validate" actually produce and how a malformed file is reported, which matters for an agent deciding how to react to the result.

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?

With one parameter at 0% schema coverage, the schema alone says only "file_path". The description compensates by constraining the expected format (ISO 10303-21) and accepted extensions (.step/.stp), which is genuinely useful semantic guidance. It does not address path form (relative vs absolute) or whether the file must already exist.

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 uses concrete verbs ("inspect and validate") on a specific resource (an ISO 10303-21 STEP file with .step/.stp extensions), so an agent knows exactly what artifact this operates on. It stops short of explicitly distinguishing itself from siblings like dfm_audit or part_build, but the file-format scoping makes its domain clear.

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 or when-not-to-use guidance and no named alternative. The words "inspect and validate" hint at intent (checking file integrity), but the agent must infer when to pick this over dfm_audit or part_build rather than being told.

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