Skip to main content
Glama

Coline

Update the workspace

update_workspace
DestructiveIdempotent

Renames a workspace or changes its description. Owners and admins only.

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": {
      "workspace": "<workspace>"
    },
    "name": "update_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
descriptionNo

Output Schema

NameRequiredDescriptionDefault
urlYes
nameYes
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, and the description usefully adds the permission requirement that annotations cannot express. However, it does not explain what the destructiveHint actually means here — whether renaming alters the slug/URLs, whether changes are reversible, or what happens to unmentioned fields — which is exactly the context a mutation tool needs.

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, action first and permission constraint second, with no filler or restatement of the title. Nothing could be removed without losing information.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and annotations cover the safety profile. Still, for a destructive mutation with a nullable field and a permission gate, the description omits null-clearing semantics and any indication of the impact of a rename, leaving real gaps.

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 description coverage is only 33%, so the description must carry weight; it does map "renames" to the name parameter and "changes its description" to the description parameter, which is genuine added meaning. It still does not clarify that passing null clears the description, nor does it add anything about the required workspace slug beyond what the schema already documents.

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?

The description gives a specific verb+resource pair ("Renames a workspace or changes its description") that maps directly onto two of the three parameters, so an agent knows exactly what the tool mutates. It does not, however, contrast itself with nearby mutators like update_settings or update_team, leaving sibling differentiation to the tool name alone.

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?

"Owners and admins only" is a real gating condition that tells the agent when the call will succeed, which is more than nothing. But there is no when-to-use vs when-not guidance, no mention of an alternative for non-owners, and no note about preconditions such as reading the current workspace first.

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