Skip to main content
Glama

list_checkins

Read-only

List check-ins for the coach (optionally filtered to one client by user _id). A check-in with status PENDING whose scheduledFor is in the past is overdue (the client did not respond).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_checkins"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 safety is covered. The description adds real domain semantics by defining overdue (PENDING status with a past scheduledFor), which is valuable context not in the annotations, but it says nothing about ordering, result volume, or pagination behavior.

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, zero filler. The primary action and scope come first, then the filter, then the overdue interpretation rule.

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 read-only list with one optional parameter and no output schema, the description covers scope, filtering, and the key interpretation rule an agent needs to use the results correctly. A brief note on ordering or result volume would make it fully complete.

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

Parameters4/5

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

Schema coverage is 0% and the schema only says clientId is a non-empty string. The description compensates by clarifying that this is a user _id used to narrow results to a single client, which is meaningfully more than the schema conveys.

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?

States a specific verb and resource ("List check-ins") plus the owning scope ("for the coach"), which is more than a restatement of the name. It does not explicitly differentiate itself from the similarly named sibling list_gym_checkins, so it falls short of a 5.

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 parenthetical explains the optional filtering behavior ("optionally filtered to one client by user _id"), which implies when to supply the parameter. There is no explicit when-to-use/when-not guidance and no routing to alternatives such as list_gym_checkins.

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.