Skip to main content
Glama

update_organization_ai_guidelines

Set the gym-wide rules the AI assistant and AI coach follow for every coach and client in the gym (confirm-gated). Replaces the whole text — read get_organization_profile first to edit rather than overwrite.

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>",
      "guidelines": "<guidelines>"
    },
    "name": "update_organization_ai_guidelines"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations only declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false. The description adds the critical trait the annotations omit: this replaces the entire guidelines text rather than merging, and the 'confirm-gated' note signals a preview-then-execute flow. The overwrite semantics are a meaningful disclosure beyond structured fields, though the lack of guidance on reversibility or who is authorized keeps it from a 5.

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?

Two tight sentences, with the operation and its overwrite hazard front-loaded and the read-first advice immediately after. There is no filler or restated boilerplate.

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?

There is no output schema, and the preview-versus-execute behavior is already carried by the 'confirm' parameter description, so the description doesn't need to explain returns. Given only three parameters, the overwrite warning plus the read-first instruction cover the main risk an agent needs to know.

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 33%, with just 'confirm' documented in the schema. The description compensates for 'guidelines' by making clear it is the whole replacement text rather than a delta, but says nothing extra about 'organizationId' beyond the gym-wide scope. That partial compensation lands at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Set the gym-wide rules the AI assistant and AI coach follow') and defines the scope as every coach and client in the gym. It is not a restatement of the tool name and stands clearly apart from profile/role update siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the confirm-gated flow and directs the agent to call get_organization_profile first when editing rather than overwriting, which is concrete when-to-use guidance tied to a named sibling. It stops short of spelling out when not to use it (e.g., partial edits), but the primary alternative is named.

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.