Skip to main content
Glama
onshape-jamcp

onshape-jamcp

Get server settings

get_settings
Read-only

Call this first to retrieve the active unit system (mm or inches), screenshot review, read-only mode, and API target, so lengths use the correct units. Never reveals API keys.

Instructions

Show this server's active settings: the unit system every length uses (metric = mm by default, or imperial = inches), whether screenshots are sent to you for visual review, read-only mode, and the Onshape API target. Never reveals API keys. Call this first so you know which unit to use for lengths.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds value beyond that by stating the confidentiality guarantee ("Never reveals API keys") and by explaining that units default to mm under metric and inches under imperial. It does not discuss caching or freshness of the settings, which keeps it short of a 5.

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?

The action is stated in the first clause and the units guidance — the most operationally important fact — is front-loaded in a parenthetical. Every clause carries new information with no restatement of the title.

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?

With no inputs, an output schema present, and read-only annotations, the description covers everything an agent needs: what it returns, the semantics of the unit value, the security guarantee, and when to call it. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description instead spends its budget on interpreting the returned values, which is more useful than parameter prose would be.

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?

Names a specific verb and resource ("Show this server's active settings") and then enumerates exactly what is returned: unit system, screenshot-review flag, read-only mode, and the API target. An agent knows precisely what this returns without opening the 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?

Gives an explicit directive — "Call this first so you know which unit to use for lengths" — which is actionable sequencing guidance rather than a vague hint. It does not name a sibling alternative, but the tool has no natural substitute given it is the only settings reader.

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