Skip to main content
Glama

Noter un entretien fait

dandori_log_maintenance

Noter qu'un entretien a été fait : la prochaine échéance se recalcule. 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": {
      "maintenance_task_id": "<maintenance_task_id>"
    },
    "name": "dandori_log_maintenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
costNoCoût
notesNo
done_atNoJour (YYYY-MM-DD), par défaut aujourd'hui
maintenance_task_idYesID de la tâche d'entretien (voir dandori_list_home)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent mutation, so the bar is lower; the description still adds two things annotations cannot convey: the automatic recalculation of the next due date and the subscription-plan requirement. It stops short of saying whether each call appends a new history entry (relevant given idempotentHint=false) or what the response contains.

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 tight clauses packed with distinct information: the action, the side effect, and the plan requirement. Nothing is repeated and the primary action leads.

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 four-parameter mutation with no output schema, the description covers the essential mechanism (logging a completed task triggers a due-date recalculation) and the access prerequisite. The remaining gap is duplicate handling and the shape of the result, which matter here because the tool is explicitly non-idempotent.

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?

With schema description coverage at 75%, the schema already documents maintenance_task_id, cost, and done_at, including the default-to-today behavior. The description adds no meaning about cost, notes, or backdating, so it neither compensates for the gap on 'notes' (undescribed in the schema) nor enriches what is already there.

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 in the first clause ('Noter qu'un entretien a été fait') and adds the consequence ('la prochaine échéance se recalcule'), so the agent knows this records a completed maintenance event rather than scheduling one. It does not explicitly contrast with siblings, but the log/record framing is clear enough to separate it from create/update style tools.

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?

Provides a real precondition ('Plan Plus requis') that tells the agent when the call will fail, which is useful gating information. It gives no when-not guidance, no mention of what to do instead for one-off or non-recurring maintenance, and no indication of what happens if the same task is logged twice.

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