List this server's toolsets
jsm_list_capabilitiesList all available Jira Service Management toolsets, show which are enabled, and identify how to load missing ones via JSM_TOOLSETS before reporting a capability is unsupported.
Instructions
Report every toolset this server knows about, whether it is currently loaded, and how to load one that is not.
Call this before telling the user something is impossible. This server carries far more of the Jira Service Management Operations API than any one install registers — the operator chooses which families load, so an absent tool usually means "not enabled here", not "not supported". This tool tells you which of the two it is, and names the exact environment variable to change.
It takes no arguments, makes no API call, and needs no credentials, so it also answers when the token is missing or wrong.
Args: none beyond response_format.
response_format ('markdown' | 'json'): default "markdown"
Returns (json format): { "requested": string[], // the names this process was configured with "read_only": boolean, "tool_count": number, // tools actually registered "toolsets": [ { "name": string, "enabled": boolean, // whether any of its tools are registered "selected": boolean, // whether the selection asked for it; false enabled with true // selected means read-only mode withheld the tools "summary": string, "scopes": string[], // OAuth scopes this family needs "tool_count": number, "tools": string[], "unverified": string // present only when the family was never seen to work } ] }
A toolset carrying unverified ships but no profile loads it, 'all' included — it has to be named on its own, as JSM_TOOLSETS=all,. The string says what blocked it: a JSM plan that excludes the feature, or a permission no credential on the test site held. Enabling it is allowed and may well work on a different site, but say what the limit was before suggesting it.
Examples:
User asks for something no loaded tool covers -> call this, then tell them which toolset covers it and that JSM_TOOLSETS needs to include it.
Tool exists but its toolset is unverified -> say so plainly, quote the reason, and let the user decide whether their plan differs.
"What can you do here?" -> call this rather than guessing from your tool list.
Note: changing JSM_TOOLSETS requires restarting the server. You cannot enable a toolset from inside a conversation.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| response_format | No | Output format. 'markdown' is compact (default); 'json' returns every field. | markdown |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| toolsets | Yes | ||
| read_only | Yes | ||
| requested | Yes | ||
| tool_count | Yes |