Skip to main content
Glama

Résumé du jour

dandori_daily_summary
Read-onlyIdempotent

Résumé du jour, court : journée (humeur, sommeil…), routines cochées ou non, tâches en retard ou du jour, en cours, prioritaires et terminées aujourd'hui, chrono, espaces du compte (Perso, Pro…) avec leurs ID. Ce que l'utilisateur garde fermé à l'IA est absent et listé dans closed_to_ai. Pour le détail des tâches : dandori_list_tasks

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context: content the user has kept closed to the AI is omitted and surfaced as a closed_to_ai list, which tells the agent to expect gaps and how they are reported. It does not describe size limits or ordering, keeping it below a 5.

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?

Two sentences, front-loaded with the summary scope and followed by the sibling routing hint. The middle enumeration is dense but each item earns its place by telling the agent what will be returned; a slightly tighter grouping would improve scanability.

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 burden of describing return contents, and it does so item by item, including the closed_to_ai field. It is complete enough to call correctly, though it omits any note on response shape or size beyond the word 'court'.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies the summary is scoped to the current day and the caller's account without inventing parameter-like options.

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 names the resource (a short daily summary) and enumerates its contents precisely: mood/sleep, routines checked or not, overdue/today/in-progress/priority/completed tasks, timer, and account spaces with their IDs. It also explicitly distinguishes itself from dandori_list_tasks, which handles task detail, so an agent can tell the two apart without opening a schema.

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?

It gives a clear routing rule: for task detail, use dandori_list_tasks, implying this tool is the compact overview. It does not state explicit when-not conditions (e.g. don't use for historical ranges or single-task lookups), so it stops short of full guidance.

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