Skip to main content
Glama

mark_gym_class_attendance

Record who attended a class session (confirm-gated). Get member userIds from get_gym_class_roster.

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": {
      "sessionId": "<sessionId>",
      "entries": "<entries>"
    },
    "name": "mark_gym_class_attendance"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
entriesYes
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The '(confirm-gated)' note is useful context but largely duplicates the schema's own confirm description ('Must be true to actually execute... returns a preview only'). For a mutation tool with readOnlyHint=false and destructiveHint=false, the description never explains the key behavioral question: whether the submitted entries replace existing attendance for the session or are merged/upserted, or what happens to members omitted from entries.

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?

Two short sentences, action first, prerequisite second, with zero filler. Nothing could be removed without losing information.

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 two-required-parameter mutation with no output schema and thin parameter documentation, the definition covers the userId sourcing path but not where sessionId comes from or what the write does to pre-existing attendance. It is callable, but an agent would be guessing at the write semantics.

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 only 33% (only confirm is documented), so the description must carry more weight. It does helpfully tie entries[].userId to get_gym_class_roster and flags the confirm gate, but leaves sessionId's source (e.g., list_gym_class_sessions), the meaning of the attended boolean, and the replace-vs-merge semantics of entries unaddressed.

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?

States a specific verb and resource ('Record who attended a class session') and immediately separates itself from the data-gathering sibling by telling the agent to use get_gym_class_roster for userIds. An agent can tell what this tool produces versus the roster tool without opening either schema.

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?

Names the prerequisite step explicitly ('Get member userIds from get_gym_class_roster'), which is concrete when-to-use guidance for the payload. It does not, however, address when to use this instead of adjacent marking tools such as mark_session_done or check_in_gym_member, nor any prerequisites beyond user IDs.

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.