Skip to main content
Glama

Switch Organization

neuron_switch_org
Idempotent

Switch to a different organization. Gets a new access token scoped to the target organization and sets it for later calls (the token is not shown).

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": {
      "orgId": "<orgId>"
    },
    "name": "neuron_switch_org"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdYesUnique identifier (UUID) of the organization to switch to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is not read-only, is idempotent, and is non-destructive. The description adds valuable context beyond them: that a new access token is obtained, that it becomes the credential for later calls, and that the token itself is not surfaced. It does not mention token lifetime or what happens to the prior session token.

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?

Two short sentences, the core action first and the side effect second. No filler.

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?

For a one-parameter context-switching tool with annotations and no output schema, this is nearly complete. Minor gaps are failure behavior on an invalid orgId and whether the previous token is invalidated.

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 single orgId parameter is fully documented in the schema as a UUID. The description adds no format or sourcing guidance for orgId, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource: switching the active organization. It is clearly distinguishable in intent from other siblings, though it does not explicitly name neuron_switch_instance or neuron_list_organizations as related tools.

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

Usage Guidelines3/5

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

Usage is implied by 'sets it for later calls' – the agent can infer this changes context for subsequent operations. However, there is no explicit when-to-use guidance, no prerequisites (e.g., needing a valid orgId from neuron_list_organizations), and no mention of when not to switch.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources