Skip to main content
Glama

send_organization_announcement

Send an announcement to a gym's coaches, clients, or everyone (confirm-gated). Irreversible: recipients get an in-app notice, and a real email if alsoEmail is true. Show the coach the exact text and audience first.

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>",
      "title": "<title>",
      "body": "<body>",
      "audience": "<audience>"
    },
    "name": "send_organization_announcement"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
titleYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
audienceYes
alsoEmailNo
locationIdNoLimit to one location
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that the action is irreversible, sends in-app notices, and sends a real email when alsoEmail is true. It also explains the confirm-gated preview workflow, which is important for a non-read-only tool.

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?

The description is compact and front-loaded: it states the action, audience scope, gating, irreversibility, and email side effect in two tight sentences. No wording feels redundant.

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 an irreversible sending tool with no output schema, the description covers the critical safety and side-effect details: confirm gating, exact text/audience review, in-app notice, and optional real email. It could still mention authorization or location scoping more explicitly, but the core completeness is strong.

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?

The description adds useful meaning for audience and alsoEmail, including the real email side effect. However, with only 29% schema description coverage across 7 parameters, it leaves other parameters such as organizationId and locationId largely to the schema and does not fully compensate.

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 gives a specific verb and resource: sending an announcement to coaches, clients, or everyone in a gym. It distinguishes this from sibling announcement tools like delete/list by its send action and audience scope.

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 provides clear usage context: this is for organization announcements and is confirm-gated, with guidance to show the exact text and audience first. It does not explicitly name when to use it instead of send_message_to_client or send_invitation, but the intended context is clear.

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.