Skip to main content
Glama
onshape-jamcp

onshape-jamcp

List custom features

list_custom_features
Read-only

Lists custom Feature Studio scripts available for adding to a Part Studio, with each feature's type, namespace, parameters, defaults and options, plus features already used.

Instructions

List custom features (Feature Studio scripts such as Thread Creator) that add_custom_feature can add: feature_type, namespace and every parameter with its type, unit, default and options. Also lists the custom features this Part Studio already uses. Built-in Onshape features are not listed - use the dedicated tools for those.

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_custom_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
element_idYesElement (tab) ID: the string after /e/ in the Onshape URL. Get it from get_document.
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.
feature_studio_urlNoOptional browser URL of a Feature Studio tab (.../documents/<did>/w|v|m/<id>/e/<eid>). Lists the custom features that studio defines instead of the ones this Part Studio already knows about. Use it for a Feature Script added to your account that is not yet in this Part Studio. To add features from another document, use its version URL (/v/).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, so safety is already covered; the description adds the substantive behavior beyond that — that it enumerates parameter metadata (type, unit, default, options) and that it reports both available and already-used features. It does not mention auth or open-world/network implications flagged by openWorldHint, but that is a minor gap for a read-only enumeration.

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-loads the scope and the return payload, then the secondary behavior, then the exclusion. Every clause carries information; the only slight redundancy is restating field-level detail that the output schema also covers.

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?

Given an output schema exists, the description needn't detail return structure, yet it does explain the field set and the two-mode behavior, plus the built-in exclusion. It would be fully complete with a one-line note on the external/open-world dependency and rate or auth expectations.

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 100%, so element_id, document_id, workspace_id and feature_studio_url are already documented in the schema, including the /e/ and /w/ URL guidance. The description adds only the conceptual split between the two listing modes, not per-parameter semantics beyond what the schema states. Baseline 3 is appropriate.

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 custom features") and then defines exactly what it returns: feature_type, namespace, and every parameter with type, unit, default and options. It also distinguishes the result from built-in Onshape features, so an agent can separate it from list_features without opening a schema.

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?

Explicitly names the consumer tool (add_custom_feature) and excludes built-ins ("Built-in Onshape features are not listed - use the dedicated tools for those"). It also explains the two listing modes: this Part Studio's known features vs. a Feature Studio URL. Missing only an explicit pointer to the exact built-in listing sibling.

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