Skip to main content
Glama

Log my daily check-in

log_daily_check_in
Idempotent

Saves today's daily check-in to the user's own Recalibrate account (requires a connected account): how they feel overall (1 to 10), whether it is a flare day and how bad, triggers, what limited them, a win, a challenge and notes. Updates today's entry if one exists. Use when the user wants to log, track or record how they are today.

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": {
      "overall_feeling": "<overall_feeling>"
    },
    "name": "log_daily_check_in"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
todays_winNo
is_flare_dayNoTrue if today is a flare day
flare_severityNoFlare severity 1-10, if a flare day
flare_triggersNoSuspected flare triggers
overall_feelingYesOverall, how the user feels today, 1 (worst) to 10 (best)
limiting_factorsNoWhat limited the user today (pain, fatigue, brain fog, sleep...)
todays_challengeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses a real prerequisite ('requires a connected account') and upsert semantics ('Updates today's entry if one exists'), which reinforces and explains the idempotentHint. One meaningful behavior is left unstated for an upsert: whether omitted optional fields are preserved or overwritten on an existing entry. That gap keeps it at 4 rather than 5.

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?

Three sentences ordered by importance: what/where it saves, then the field inventory, then the upsert behavior and the invocation cue. No filler, and the critical account prerequisite sits inline rather than buried.

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?

With no output schema, the description carries the return-side burden, and 'saves' plus upsert behavior is enough for an agent to act. Account requirement is covered, but partial-update semantics and confirmation of what the call returns are not, leaving a modest gap for an 8-parameter mutation.

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 63%, with notes, todays_win and todays_challenge carrying no schema descriptions; the description names all of these along with triggers, limiting factors, flare severity and overall feeling, so the agent gets a complete picture of the loggable payload. It does not add scale or format meaning beyond what the schema already states for the scored fields, and it never says only overall_feeling is required.

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?

The description opens with a specific verb and resource ('Saves today's daily check-in to the user's own Recalibrate account') and scopes it to today, so an agent immediately knows the write target and the record's time window. The enumeration of what the check-in holds confirms the resource identity, and no sibling tool competes for this action.

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?

'Use when the user wants to log, track or record how they are today' gives a clear, concrete trigger condition tied to user intent. It stops short of exclusions (e.g., not for viewing history or patterns, which siblings like get_my_patterns cover), so it is clear but not fully routed.

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.

Resources