Skip to main content
Glama

record_organization_coach_attendance

Mark a coach present/absent/late/on-leave at a location for a date (confirm-gated).

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>",
      "coachId": "<coachId>",
      "locationId": "<locationId>",
      "attendanceDate": "<attendanceDate>",
      "status": "<status>"
    },
    "name": "record_organization_coach_attendance"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
statusYes
coachIdYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
locationIdYes
attendanceDateYesYYYY-MM-DD
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?

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation/safety profile is covered; the description adds that marking is confirm-gated. However, it does not disclose whether re-recording for the same coach/date overwrites an existing record, what happens to the previous status, or what a preview contains.

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?

A single front-loaded sentence with the action, the resource, the allowed states, and the confirm constraint; no filler or redundant restatement of the title.

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 7-parameter mutation with no output schema and low schema coverage, the description covers the core intent but omits duplicate/overwrite behavior and the meaning of the notes field. It is minimally sufficient to call the tool but leaves real ambiguity about idempotency.

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 coverage is only 29%, and the description clarifies the status domain and the location/date scoping, which maps to three of the seven parameters. It says nothing about notes, organizationId, coachId, or the semantics of re-recording, so the remaining undocumented parameters are left to the bare schema.

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 states a specific verb (mark) and resource (coach attendance) plus the scope of a location and a date, and it enumerates the valid states (present/absent/late/on-leave). It is clearly the write counterpart to the sibling get_organization_coach_attendance, though it never names that sibling explicitly.

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?

The phrase '(confirm-gated)' hints that execution requires a confirmation step, which implies a two-call workflow, but the description never says when to use this versus get_organization_coach_attendance or mark_gym_class_attendance, and gives no prerequisites or exclusions.

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.