Skip to main content
Glama

Update group details

update_group
Destructive

An organizer replaces the group name, description, visibility and admission policy. Read get_my_group first and keep any fields the player did not ask to change. Requires mcp:manage.

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": {
      "token": "<token>",
      "name": "<name>",
      "visibility": "<visibility>",
      "admission": "<admission>"
    },
    "name": "update_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
tokenYes
admissionYes
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
visibilityYes
descriptionNo
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so the agent knows this is a mutating call; the description adds value on top by disclosing the replacement (not patch) semantics and the authorization scope required. The 'keep any fields' instruction effectively warns that omitted fields get overwritten. It does not say what happens to members or other group state, which is the remaining disclosure gap.

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 sentences, zero filler, and the most decision-relevant fact (replacement semantics) is front-loaded before the workflow advice. Every clause earns its place.

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 destructive 7-parameter mutation with no output schema, the definition covers the essentials: what is replaced, the read-before-write requirement, and the required scope. It is slightly thin on the unspecified parameters and on the effects of the update beyond the group record itself, but an agent could call this correctly from the description.

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 29%, so the description carries extra burden, and it partially does by naming four of the seven parameters and clarifying that untouched fields must be preserved. However, the named fields are already typed and enum-constrained in the schema, and the description says nothing about token, llm_model, or conversation_id. Net added meaning over the schema is modest.

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 opens with a specific actor (organizer), verb ('replaces'), resource (group) and enumerates the mutable fields (name, description, visibility, admission policy). That is enough for an agent to tell this apart from create_group or update_event without opening a schema. It stops short of explicitly naming an alternative update path, but the resource is unambiguous.

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?

It gives a concrete prerequisite ('Read get_my_group first') and a workflow rule ('keep any fields the player did not ask to change'), which is real when-to-use guidance rather than a restatement. It also states the required scope 'mcp:manage'. There is no explicit when-not-to-use, but for a single-purpose mutation that is a minor gap.

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