Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

changeOrg

Switch the active organization by ID so DICloak profile, group, proxy, and member operations apply to the intended workspace.

Instructions

Switch organization

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": {
      "id": "<id>"
    },
    "name": "changeOrg"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.6/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not say whether switching changes global session state, affects subsequent tool calls, requires permissions, or is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but this is under-specification rather than conciseness. A two-word phrase cannot carry the state-changing semantics of an organization switch.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even for a single-parameter tool, there is no output schema, no annotations, and no description of the parameter or the resulting session state. Nothing an agent needs in order to invoke it correctly is present.

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

Parameters1/5

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

Schema description coverage is 0% and the description adds no parameter meaning. The single required field "id" is undocumented — it could be an organization ID, a numeric handle, or a name — leaving the agent with no basis for supplying a valid value.

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

Purpose3/5

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

"Switch organization" states a verb and a resource, so the intent is inferable, but it does not say what is being switched (account context? session scope?) or how it differs from the sibling environment/proxy tools. It is barely more than a name expansion, though not a pure tautology.

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

Usage Guidelines1/5

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

There is no guidance at all on when to call this versus any alternative, no mention of prerequisites such as being authenticated, and no explanation of what state changes afterward. The agent is left to guess from the name alone.

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