Skip to main content
Glama

Get Daily Checkin

get_daily_checkin

Get a single day's rollup of weight, sleep, workout minutes, recovery, and lifting by date to review personal health and training status.

Instructions

Single-day rollup: weight, sleep, workout minutes, recovery and lifting.

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": {
      "date": "<date>"
    },
    "name": "get_daily_checkin"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate as YYYY-MM-DD

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about behavior beyond what is returned. It does not state what happens for a date with no entries (error vs. zeroed fields), whether the call is cached or read-only, or what 'recovery' and 'lifting' represent as values. The presence of an output schema covers return shape, but not operational behavior.

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?

One short clause, front-loaded with the scope word 'Single-day' and then the metric list; nothing is redundant. It is arguably compressed to the point of being a fragment rather than a sentence, but there is no filler.

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?

The tool is simple (one required date, output schema present), so the description is not grossly incomplete. However, for an agent choosing among eight health-metric siblings, it omits missing-data behavior and the boundary against get_overview, which are the two things most likely to cause a wrong call.

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?

There is a single parameter whose schema coverage is 100%, with a regex pattern and an explicit 'YYYY-MM-DD' description, so the schema fully documents it. The description adds no further meaning, such as whether future dates are allowed or how time zones are treated, so the baseline 3 applies.

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 gives a concrete resource and scope: a 'single-day rollup' that enumerates the metrics returned (weight, sleep, workout minutes, recovery, lifting). It is clear what the tool returns and at what granularity, but it never distinguishes itself from siblings like get_overview or get_lifting_summary, which likely overlap in content.

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?

'Single-day' weakly implies daily granularity, but there is no statement of when to prefer this over get_overview, get_lifting_summary, or get_sleep_training_correlation. There are also no prerequisites or exclusions, so an agent must infer selection from tool names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.