Check Onshape connection
whoamiVerify configured Onshape credentials by identifying the connected account, confirming API keys or OAuth sign-in work, and distinguishing bad keys from bad document IDs when a 401 occurs.
Instructions
Check that the configured credentials (API keys or OAuth sign-in) really work, by asking
Onshape which account they belong to: returns connected, user_id, name and the base_url in
use. Use it first in a session or whenever another tool answers 401, and to tell a wrong
key from a wrong document ID. Read-only, one request, nothing is changed. Onshape answers
200 with an empty body to credentials it does not recognise, so this call treats that
"anonymous" reply as a failure and explains how to fix the keys. It does not show which
permissions (read / write / delete) the key has - a 403 from a modeling tool means the key
lacks the write scope. For this server's own settings use get_settings.
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": "whoami"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||