Skip to main content
Glama

create_organization

Create a new organization (confirm-gated) — the coach becomes its owner.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description's job is to add mutation detail beyond that. It does: it discloses the two-phase confirm gate and the ownership side effect ("the coach becomes its owner"), both of which are non-obvious. It omits uniqueness rules for the name and what a failed or duplicate create does.

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?

A single em-dash clause pair, front-loaded with the action and immediately followed by the two facts an agent needs (confirm gate, ownership). No filler or restatement of the tool name.

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 two-parameter mutation with no output schema and clear annotations, this covers the essentials: what is created, what the caller becomes, and that execution is confirm-gated. Remaining gaps (name uniqueness, return payload, auth requirements) are minor for this complexity.

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 coverage is 50%: confirm is fully documented in the schema, while name carries only minLength 1 and no semantics. The description echoes the confirm gate and explains the implicit owner assignment, but adds nothing about name validation, uniqueness, or formatting, so it only partially compensates for the gap.

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?

Names a specific verb and resource ("Create a new organization") and adds the ownership outcome, which separates it from sibling creates like create_organization_custom_role and create_organization_location by resource alone. It never explicitly contrasts with those siblings, so it stops short of a 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 "(confirm-gated)" parenthetical implies the caller must set confirm=true to execute, which is useful usage context. However, it gives no explicit when-to-use vs. when-not guidance, no prerequisites (e.g., caller must already be a coach/owner, org limits), and no named alternatives.

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.