Skip to main content
Glama

group_create

Create a new Operaton group with an ID, name, and optional type to manage candidate task assignments and authorization.

Instructions

Create a new Operaton group with an id, name, and optional type. Groups are used to manage candidate task assignments and authorization.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • addedInput schema / additionalProperties
      Added value: +{}
  2. First observedv1.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a mutation ('Create a new') but says nothing about required authorization, whether the caller or server assigns the id, what happens if the id already exists, or whether the change is reversible — significant gaps for a write tool with zero annotation coverage.

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, front-loaded with the action and the fields, followed by one line of domain context. Nothing is redundant and nothing buries the operative 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?

For a low-complexity create tool with no output schema, the description covers the resource and its fields adequately. It omits required-field marking, duplicate-id behavior, and return value, which leaves the agent guessing at call semantics even though the tool itself is simple.

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?

The schema declares an empty properties object with additionalProperties: {}, so the description is the only place an agent learns the accepted fields are id, name, and type, and that type is optional. That is real added meaning, though it lacks formats, constraints, or a statement of which fields are mandatory.

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 concrete verb+resource pair ('Create a new Operaton group') and enumerates the fields that define the resource (id, name, optional type), so an agent knows exactly what the tool produces. It stops short of naming sibling alternatives, but the create-vs-addMember-vs-delete distinction is already unambiguous from the verb.

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 second sentence ('Groups are used to manage candidate task assignments and authorization') supplies the business context for why an agent would create a group, which is implied usage guidance. It never states prerequisites, required permissions, or when to prefer a different tool, so the guidance remains inferred rather than explicit.

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

Deploy Server

Other Tools