Skip to main content
Glama

list_organization_announcements

Read-only

Announcements previously sent to a gym's coaches and/or clients, with audience and reach.

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

Input Schema

NameRequiredDescriptionDefault
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that results reflect already-sent announcements and carry audience/reach fields, but says nothing about pagination, ordering, volume, or permissions — modest value beyond annotations.

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 no filler, and the most distinctive detail (audience and reach) is placed at the end. It is efficient but slightly under-packed for a tool description rather than verbose.

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 read-only, single-parameter list tool with annotations and no output schema, minimal description is defensible, and the audience/reach hint covers return shape at a high level. Still missing are pagination/ordering behavior and any statement of scope that would let an agent call it with confidence.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the single organizationId parameter is documented only by its name and type. The description never explains that organizationId is the gym/org scope, whether announcements are tenant-wide, or any format expectations, leaving the low-coverage schema without compensation.

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

Purpose3/5

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

The fragment identifies the resource (announcements previously sent to a gym's coaches and/or clients) and hints at return content (audience and reach), which distinguishes it from siblings like list_organization_clients. However, it is a noun phrase with no verb, so it restates the operation implicitly rather than stating what the tool does with those announcements.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives. Usage is only inferable from 'previously sent', which implies a historical/read view, but an agent gets no routing signal among the many list_organization_* siblings.

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.