Skip to main content
Glama

Noter le check-in du jour

dandori_log_checkin
Idempotent

Noter la journée dans le check-in : humeur, énergie, gratitudes, sommeil, eau, activité physique. Seuls les champs fournis changent ; null efface une valeur

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": "dandori_log_checkin"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoJour (YYYY-MM-DD), aujourd'hui ou passé ; par défaut aujourd'hui
moodNoHumeur, de 1 (très mal) à 5 (super)
notesNo
energyNoÉnergie, de 1 (à plat) à 5 (pleine forme)
gratitudesNoJusqu'à trois gratitudes (la liste remplace l'ancienne)
sleep_hoursNoHeures de sommeil
sleep_bedtimeNoCoucher (HH:MM)
sleep_qualityNoQualité du sommeil, 1 à 5
exercise_typesNoActivités (ex. course, yoga)
sleep_wake_timeNoLever (HH:MM)
exercise_minutesNoMinutes d'activité physique
hydration_litersNoEau bue, en litres
exercise_intensityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the write-and-repeat-safely profile is covered. The description adds the important merge semantics ('seuls les champs fournis changent') and the erase-on-null rule, which annotations cannot express — though it says nothing about authentication, whether a missing day is created, or what comes back.

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 clauses, no filler: the first front-loads what is recorded, the second states the update contract. Every sentence earns its place and nothing is redundant with 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 13-parameter mutation with no output schema, the definition covers the field domains and the merge/null contract, which is the core risk. It leaves open whether a check-in for a new date is created versus rejected, and gives no indication of the response, so an agent cannot fully predict the outcome.

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 description coverage is 85%, so most of the 13 parameters are already documented. The description still contributes meaning the schema does not: that omitted fields are preserved and that null explicitly clears a stored value — a distinction an agent would otherwise get wrong when passing null.

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 ('Noter') and resource ('le check-in du jour') and enumerates the domains covered (humeur, énergie, gratitudes, sommeil, eau, activité physique). That field list implicitly separates it from siblings like dandori_log_calories, dandori_log_weight or dandori_log_learning_session, but no sibling is named to make the boundary explicit.

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 sentence 'Seuls les champs fournis changent' tells the agent this is a partial/upsert-style write, which is real usage guidance. However there is no explicit statement of when to pick this tool over the neighbouring log_* tools, nor any note on allowed date ranges beyond what the schema already says.

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