Skip to main content
Glama

Noter une pesée

dandori_log_weight
Idempotent

Noter une pesée ; une seule par jour, une deuxième le même jour remplace la première. Plan Plus requis.

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": {
      "weight_kg": "<weight_kg>"
    },
    "name": "dandori_log_weight"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoJour (YYYY-MM-DD), aujourd'hui ou passé ; par défaut aujourd'hui
weight_kgYesPoids en kilos, au dixième près

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that a same-day entry overwrites the previous one (important data-replacement behavior for a write tool) and that a paid plan is required. The annotations already declare idempotentHint=true and destructiveHint=false, and the overwrite rule is consistent with them rather than contradictory. It stops short of describing what is returned or what happens on validation failure.

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?

A single compact sentence-cluster separated by semicolons, front-loading the action and then the per-day rule and prerequisite. No filler or repetition, though the punctuation is dense enough that the plan requirement reads as an afterthought.

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 two-parameter write tool with no output schema and full annotation coverage, the description supplies the essential extras: daily uniqueness, overwrite semantics, and a subscription prerequisite. Only the failure/validation behavior and return confirmation are unstated, which is minor at this complexity.

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 coverage is 100%, so both parameters (date with YYYY-MM-DD and default-today semantics, weight_kg with 30–300 bounds and one-decimal precision) are already fully documented. The description adds only the daily-uniqueness constraint, which implicitly governs the date parameter but adds no format or range detail beyond the schema. Baseline 3 is appropriate.

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 opens with a specific verb and resource ("Noter une pesée"), which unambiguously identifies a weight-logging action distinct from unrelated siblings such as dandori_log_learning_session or dandori_add_transaction. It does not explicitly contrast with the closest sibling (dandori_log_calories), so it stops 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?

It states the key usage constraint — one entry per day, with a second entry the same day replacing the first — and a prerequisite (Plan Plus requis). However, it gives no explicit when-to-use vs. when-not-to-use guidance or named alternative for correcting or backfilling historical data.

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