Skip to main content
Glama

get_organization_coach_attendance

Read-only

A location's coach attendance roster for one date.

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>",
      "attendanceDate": "<attendanceDate>"
    },
    "name": "get_organization_coach_attendance"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdNo
attendanceDateYesYYYY-MM-DD
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds only that results are scoped to a single location and a single date; it says nothing about permissions, whether locationId is optional and what happens when omitted, or date/timezone interpretation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no filler, but it is under-specified rather than concise. The scoping information (location, date) is front-loaded, yet the missing verb makes it read like a title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter read tool with no output schema, the description should clarify what the roster contains, whether locationId is optional, and how the date bounds the result. None of that is present, so the agent must guess at call semantics.

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 coverage is only 33% — just attendanceDate carries 'YYYY-MM-DD'. locationId and organizationId are undocumented, and the description does not compensate: it hints at a location filter but never explains that locationId is optional or how organizationId scopes the query.

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 'A location's coach attendance roster for one date' identifies the resource (coach attendance) and its scope (one location, one date), so an agent can roughly place it. But it is a noun phrase with no verb, leaving it ambiguous whether it retrieves, lists, or summarizes, and it never distinguishes itself from the write counterpart record_organization_coach_attendance.

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 when-to-use guidance at all: nothing says to call this for reading attendance versus record_organization_coach_attendance for writing it, or versus get_gym_attendance_summary for aggregates. The only implicit cue is the word 'roster'.

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.