Skip to main content
Glama

Lire un bilan de la semaine

dandori_get_weekly_review
Read-onlyIdempotent

Lire le bilan d'une semaine (chiffres, notes, réflexion) ; sans date, le dernier pas encore lu

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_get_weekly_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
week_startNoLundi de la semaine (YYYY-MM-DD)

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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one non-obvious behavior beyond that: with no date it returns the most recent not-yet-read review. It does not resolve whether fetching a 'pas encore lu' review marks it as read (a state change that would sit uneasily with readOnlyHint), nor what happens when no unread review exists.

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?

A single compact sentence, front-loaded with the verb and resource, with the optional-parameter default attached after a semicolon. No filler and nothing that merely restates 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 one-parameter, read-only tool with no output schema and full schema coverage, the description covers purpose and default selection adequately. It leaves open the read-tracking side effect and the empty-result case, which matter for an agent deciding whether re-calling is safe or whether it should fall back to a dated request.

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 100% and the single parameter already documents the format (Lundi de la semaine, YYYY-MM-DD), so the baseline would be 3. The description earns the extra point by explaining the semantics of omitting week_start entirely — the latest unread review — which the schema does not convey for an optional parameter.

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 ('Lire le bilan d'une semaine') and even enumerates the payload ('chiffres, notes, réflexion'), which lets an agent distinguish it from the write-oriented sibling dandori_write_weekly_review. It stops short of naming the sibling explicitly, so differentiation relies on the read/write verb pair in the tool names.

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 trailing clause 'sans date, le dernier pas encore lu' tells the agent when omitting the parameter is appropriate, which is genuine usage guidance for the common path. There is no statement of when-not to use it, nor any pointer to an alternative tool for past or listed reviews.

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