Skip to main content
Glama

Create a group

create_group

Creates a group with the specified name, listing visibility and admission policy. Confirm those choices before creating it. 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": {
      "name": "<name>",
      "visibility": "<visibility>",
      "admission": "<admission>"
    },
    "name": "create_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
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

A3.6/5.0
Behavior4/5

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

Beyond the annotations, which already say this tool is a non-destructive write that is open to the outside world, the description discloses the mcp:manage permission prerequisite and a mandatory confirmation workflow before the mutation. It does not say what happens on a duplicate name, whether the creator is auto-joined, or what the call returns; those gaps keep it at 4.

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?

Three short sentences with no padding, and the required action, confirmation instruction, and permission note are presented in that order. The opening clause slightly restates the title but is not wasteful.

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?

For a creation tool with a medium-complexity six-parameter schema, no output schema, and no documentation of a third of the parameters, the description covers the essentials of how to invoke it, but not what the agent should expect: no return value, no duplicate handling, and no post-condition information.

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?

With only 33% schema description coverage, the description compensates partially: it names the three required parameters (name, visibility, admission) and clarifies that visibility governs the listing. The enum meanings (public/private, automatic/approval) and the analytics parameters llm_model and conversation_id are left entirely to the schema.

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 (creates) and resource (group) and names the three required attributes: name, listing visibility, and admission policy. It is distinguishable from update_group or get_my_group, but it does not explicitly contrast with those siblings, so it falls just short of 5.

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?

The description implies when to use the tool: before creating the group, it requires a confirmation step. It also names the needed permission (mcp:manage). It never says when not to use it or point to an alternative such as join_group or update_group, leaving usage context largely inferred.

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