Skip to main content
Glama
onshape-jamcp

onshape-jamcp

List features

list_features
Read-only

Retrieves a Part Studio's ordered feature tree with IDs, types, suppression, health, and rollback index, helping locate features to update or delete and diagnose modeling errors.

Instructions

List the feature tree of a Part Studio in order: features with feature_id, name, feature_type (newSketch, extrude, fillet, ...), suppressed and health status (OK / WARNING / ERROR), plus the rollback_index. Use it to find the feature_id that update_feature or delete_feature needs, to see why a part looks wrong (an ERROR feature built no geometry), or - with feature_id - to read one feature's full raw JSON as a template for add_feature or to learn its parameter IDs. The modeling tools already return the health of the feature they add, so do not call this after every step: Onshape limits this endpoint per day (a free plan can hit a 429 with a many-hour wait after heavy polling). Read-only. For the parts it produces use list_parts; for variables list_variables.

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": {
      "document_id": "<document_id>",
      "element_id": "<element_id>"
    },
    "name": "list_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
element_idYesElement (tab) ID: the string after /e/ in the Onshape URL. Get it from get_document.
feature_idNoIf set, return the full raw JSON of just this feature (useful as a template for add_feature or to see its parameter IDs for update_feature).
document_idYesOnshape document ID: the 24-character hex string after /documents/ in the document URL. Get it from list_documents.
workspace_idNoWorkspace ID (the string after /w/ in the URL). Optional - defaults to the document's main workspace.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description still adds real value: a per-day endpoint quota that can trigger a 429 with a many-hour wait on a free plan, and the semantics that an ERROR feature produced no geometry. What it does not cover is how the tree is ordered or paginated, though the ordering is implied by 'in order'.

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?

Front-loaded with what is returned, then use cases, then the throttling warning, then cross-references — a sensible priority order. It is dense rather than padded, though the feature_id templating guidance appears twice (once in prose, once in the schema) and the sentence could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values are covered structurally; the description still summarizes the shape usefully. For a read-only, four-parameter, quota-limited endpoint, it supplies usage triggers, alternatives, and the rate-limit risk — nothing important an agent needs before calling is missing.

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% and the schema already documents document_id, element_id, workspace_id, and the feature_id mode switch, including the 'template for add_feature' rationale. The description restates the feature_id behavior (return one feature's full raw JSON) but adds no syntax or format detail beyond the schema, so the baseline applies.

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

Purpose5/5

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

States a specific verb and resource ('List the feature tree of a Part Studio') and enumerates exactly what each entry contains: feature_id, name, feature_type with example values, suppressed, health status, plus rollback_index. This is precise enough that an agent knows what it gets back without opening the output schema, and it is clearly distinct from siblings like list_parts and list_variables.

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

Usage Guidelines5/5

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

Gives three concrete use cases (look up a feature_id for update_feature/delete_feature, diagnose an ERROR feature that built no geometry, fetch raw JSON as a template for add_feature) and an explicit when-not-to-use rule: don't call after every modeling step because the modeling tools already return health. It also routes to list_parts for geometry and list_variables for variables.

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