Skip to main content
Glama

Update the organization

update_organization
Idempotent

Rename the organization (workspace) these credentials act for, or switch it between artist, label and creator Owners and admins only. An artist workspace can become a label or creator workspace any time, and those can switch between each other; they can become an artist workspace only while they have one artist or none (409 otherwise).

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

Input Schema

NameRequiredDescriptionDefault
nameNoThe new workspace name
typeNoartist (one artist), label (a roster) or creator (projects)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"artist (one artist) or label (a roster)"New value: +"artist (one artist), label (a roster) or creator (projects)"
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "artist",
      -  "label"
      -]New value: +[
      +  "artist",
      +  "label",
      +  "creator"
      +]
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description adds the permission requirement, the 409 failure condition, and the asymmetric transition rules - notably that converting back to an artist workspace is blocked while more than one artist exists. This is meaningful operational context an agent cannot get from the annotations.

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

Conciseness4/5

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

Two sentences, front-loaded with the two capabilities followed by the constraints. The second sentence is fairly dense and slightly run-on, but every clause carries distinct operational information and nothing is wasted.

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 two-optional-parameter mutation with no output schema, the definition covers purpose, permissions, error behavior and transition rules thoroughly. The only gap is that with zero required parameters it never states the effect of omitting name, type, or both.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains the consequences of choosing a type (the transition constraints and 409 case) rather than merely restating the enum labels. It does not clarify what happens when either optional parameter is omitted, which keeps it from a 5.

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?

States a specific verb and resource - rename the organization/workspace and switch it between artist, label and creator - and clearly scopes it as the org these credentials act for, distinguishing it from create_organization, list_organizations and the rename_artist/rename_song siblings.

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 explicit preconditions for use (Owners and admins only) and precisely when each type transition is permitted versus rejected with 409. It does not name an alternative tool or explain when to avoid the operation entirely, so it falls just short of a 5.

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