Skip to main content
Glama

update_organization_location

Rename or re-address an existing location (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": {
      "locationId": "<locationId>",
      "name": "<name>",
      "address": "<address>"
    },
    "name": "update_organization_location"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is largely covered. The description adds the useful 'confirm-gated' trait, signaling a two-step workflow, but it does not say what the update affects (e.g., whether existing bookings or coach assignments tied to the address are impacted) or what permissions are required.

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 tight sentence with the core action front-loaded and the confirm-gate qualifier at the end. Nothing is wasted, though the extreme brevity leaves little room for routing context.

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 simple four-parameter mutation with an existing annotation set and a schema that documents the confirm flag, this is minimally sufficient. It falls short on side effects and permission requirements, which matter for an operation that changes an organization's address.

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%, so the description carries more burden than usual. 'Rename or re-address' maps meaning onto the name and address parameters, and 'confirm-gated' aligns with the confirm flag, but locationId receives no explanation and no format or validation detail is added beyond the schema's minLength constraints.

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 names a specific verb pair ('rename or re-address') and a specific resource ('an existing location'), which cleanly separates it from create_organization_location and delete_organization_location. It does not explicitly name those siblings, so the differentiation is inferential rather than stated.

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?

'Existing location' implies this is for modifying rather than adding a location, and 'confirm-gated' hints at a preview-then-execute flow. However, there is no explicit statement of when to choose this over create/delete or update_organization, and no prerequisites or exclusions are given.

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.