Skip to main content
Glama

create_organization_location

Add a new location/branch to an organization (confirm-gated).

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": {
      "organizationId": "<organizationId>",
      "name": "<name>",
      "address": "<address>"
    },
    "name": "create_organization_location"
  }
}

Input Schema

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

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 declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false but say nothing about confirmation flow. The parenthetical 'confirm-gated' adds real behavioral context beyond the annotations, alerting the agent that a preview/confirm cycle exists. It stops short of describing what a preview returns or what permissions are needed.

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?

One short sentence with the action front-loaded and the confirm-gating constraint attached, no filler. It is terse but every clause earns its place; slightly more detail could be added without bloat.

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 mutating tool with no output schema and no annotations covering side effects, the description covers the action and the confirm gate but leaves out permission requirements and what a preview response contains. Adequate but with clear gaps.

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 only 25%, with just the confirm parameter documented. The description implies organizationId by saying 'to an organization' but adds no detail on name or address formats. The remaining fields are largely self-explanatory, so this is a baseline-middling score rather than a failing one.

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 states a specific verb and resource: 'Add a new location/branch to an organization.' That is enough for an agent to distinguish it from update_organization_location and delete_organization_location by the word 'new,' though it never names those siblings explicitly.

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?

'confirm-gated' signals that this is a two-step operation, which is useful usage context, but the description gives no explicit when-to-use or when-not-to-use guidance relative to the update/delete siblings or any prerequisites such as permissions.

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.