Skip to main content
Glama

list_organization_coaches

Read-only

List coaches in an organization, optionally filtered to one location, with each coach's client count and revenue.

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_coaches"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdNo
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already state readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral content beyond that — it discloses that each result carries a client count and revenue figure — but says nothing about pagination, result caps, or authorization requirements.

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 well-formed sentence with no redundant wording, and the core action is front-loaded before the optional filter and return fields. Nothing needs trimming.

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 a two-parameter read-only list tool with no output schema, the description covers the action, the optional filter, and the shape of returned data. The remaining gap is pagination/volume behavior, which is minor here.

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 0%, so the description must carry the burden. It explains that locationId is an optional single-location filter, but organizationId is only implied by 'in an organization' and neither parameter's format or ID source is clarified.

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 and resource ('List coaches in an organization') and adds scope detail: optional single-location filtering plus the returned fields (client count and revenue). It is clearly distinguishable from siblings like bulk_import_gym_coaches, though it does not explicitly name or contrast an alternative tool.

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?

Usage is implied by the phrasing — use it to enumerate coaches in an organization, optionally narrowed to a location. There is no explicit when-to-use versus when-not guidance and no mention of prerequisites such as org-level permissions, which the sibling set (invite/remove coach tools) makes relevant.

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.