Skip to main content
Glama

update_organization_profile

Update a gym's profile (confirm-gated). Only the fields you pass change. isPublic publishes or unpublishes the gym's public page; brandingEnabled/brandColor apply the gym's brand to every coach's client-facing surfaces.

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

Input Schema

NameRequiredDescriptionDefault
cityNo
nameNo
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
isPublicNo
brandColorNoHex colour, e.g. #1F6FEB
descriptionNo
contactEmailNo
contactPhoneNo
organizationIdYes
brandingEnabledNo
communityEnabledNo

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?

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses the blast radius of specific fields: isPublic publishes/unpublishes a public page, and brandingEnabled/brandColor propagate to every coach's client-facing surfaces. That side-effect disclosure is exactly the kind of context annotations cannot convey. It stops short of covering other write effects (e.g. communityEnabled, contact fields) or response shape.

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?

Three sentences, front-loaded with the action and the confirm gate, then the partial-update rule, then the field-specific effects. Dense and purposeful; the parenthetical gating note and the branding clause both earn their place. Slightly compressed phrasing but no waste.

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 an 11-parameter mutation tool with no output schema and low schema coverage, the description covers the risky fields and the confirm workflow but is silent on the remaining parameters and on what a successful update returns. Adequate to call safely, not complete.

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?

With only 18% schema coverage across 11 parameters, the description does meaningful work for three of them (isPublic, brandingEnabled, brandColor) and states the partial-update semantics that governs them all. It leaves city, name, description, contactEmail, contactPhone, communityEnabled, and organizationId without any added meaning, so the compensation is partial rather than complete.

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?

States a specific verb and resource ('Update a gym's profile') and immediately qualifies it with the confirm-gated semantics. It is not explicitly differentiated from the sibling update_organization, but the 'profile' framing plus the field-level notes make the scope distinguishable enough for selection.

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)' note and 'Only the fields you pass change' imply the intended partial-update workflow, which is useful guidance. However there is no statement of when to choose this over update_organization, update_organization_ai_guidelines, or update_organization_location, and no prerequisites 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.