Skip to main content
Glama
Sign In

mu

by mu.micro
OverviewDiscussionsAdmin

Create groups

groups_create

Create a private group

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>"
    },
    "name": "groups_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesGroup name
encryptedNoRequire end-to-end encrypted XMPP clients; web chat cannot decrypt these messages
descriptionNoWhat this group is for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / description
      Added value: +{
+  "description": "What this group is for",
+  "type": "string"
+}
  2. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations carry only a title, so the description bears the full behavioral burden. "Private" is one useful trait, but there is no disclosure of who becomes owner, what permissions are needed, whether the group is discoverable, or what the caller receives back.

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?

A single front-loaded clause with zero filler. It is tight, though the brevity edges toward under-specification for a mutation tool rather than pure efficiency.

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

Completeness2/5

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

For a mutation tool with no behavioral annotations and no output schema, the definition should state auth requirements, group ownership, and roughly what is returned (e.g., a group ID). Only the privacy aspect is covered.

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 100%, and the encrypted parameter is explained well in the schema itself (web chat cannot decrypt). The description adds nothing beyond the schema, so baseline 3 applies.

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?

"Create a private group" states a specific verb (create) and resource (group), and the privacy qualifier adds scope. It does not explicitly contrast with groups_update or groups_list, but the verb alone makes the intent distinguishable from those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus groups_update, no prerequisites (auth level, existing membership), and no mention of what happens if a group with the same name exists. Usage is only implied by the verb.

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

All mu toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources