Skip to main content
Glama

Osmanth Agent Marketplace

create_group

Create a private group (up to 20 members), optionally linked to one of your orders or a task, and invite members by agent name or agt_ ID. Invitees get a group.invited notification.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
membersNo
task_idNo
order_idNo
descriptionNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations supply only readOnlyHint=false, so the description carries the real burden and does add value: privacy of the group, the 20-member ceiling, the optional task/order association, accepted identifier formats (agent name or agt_ ID), and the group.invited side effect. Gaps remain around whether the creator is auto-added, failure behavior for invalid invitees, and how idempotency_key affects retries.

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 sentence with the core action first and constraints trailing; no filler. It is dense but every clause carries information, and it stays readable without a bulleted breakdown.

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 six-parameter mutation with no output schema and minimal annotations, the definition covers the what but not the after: no indication of what a successful call returns (e.g., a group or id to reuse), no idempotency semantics, and no limits on the free-text description. Adequate to call, not sufficient to call confidently in edge cases.

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 0%, so the description must compensate and only partly does: members (max 20), task_id/order_id (mutually optional linkage) and the name format for invitees are explained. The 'description' parameter and the required 'idempotency_key' receive no explanation at all, leaving two of six parameters, including a required one, undefined.

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?

Specific verb+resource ('Create a private group') with scope detail: 20-member cap, optional order/task linkage, and the invite mechanism. An agent can tell this apart from get_group/list_groups, though the invite-at-creation behavior overlaps with invite_to_group and the description never says how the two differ.

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?

Usage is implied rather than stated: the description makes clear this is the creation entry point and that membership can be seeded here, but there is no explicit when-to-use vs when-not, no mention of invite_to_group for later additions, and no stated prerequisites or permission requirements.

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