Skip to main content
Glama

KinetiCAD CNC Parts

Look at a part

view_part
Read-onlyIdempotent

Get a picture of a part from one side, with its measured size and features. Use it to check that the part is what the user asked for before you price or order it.

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": {
      "part_id": "<part_id>"
    },
    "name": "view_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoThe side to look from. iso looks down from the front right; under shows the underside.iso
part_idYesThe part_id that build_part (or the HTTP upload of a STEP file) returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description adds useful detail that the return is a visual plus measurements and features, and no output schema exists to state that otherwise, but it says nothing about rendering latency, failure modes, or whether a missing/invalid part errors.

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?

Two sentences, front-loaded with what is returned and followed by the workflow condition for calling it. No redundant restatement of the name or the schema.

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 read-only, two-parameter render tool with no output schema, the description supplies the crucial missing piece: what comes back (an image with measured size and features). Only edge-case behavior, such as invalid ids or what a given view shows when features are hidden, is left unstated.

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 coverage is 100%: both part_id (24-char id from build_part) and the view enum with per-value meanings are fully documented in the schema. The description only echoes the "one side" notion behind view, so it stays at the baseline rather than adding new semantics.

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?

"Get a picture of a part from one side, with its measured size and features" names a specific verb (get/render a view) and resource (part) plus the payload content. It is clearly distinct from build_part, price_part and request_order, though it never names a sibling explicitly.

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?

It gives a concrete usage point in time: "Use it to check that the part is what the user asked for before you price or order it," which sequences it ahead of price_part and request_order. It stops short of stating when not to use it (e.g. when only a build is needed).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources