Skip to main content
Glama

Rappels à venir

dandori_upcoming_reminders
Read-onlyIdempotent

Rappels de tâches des trois prochains jours (heure du rappel en UTC, tâche), plusieurs par tâche s'il y a lieu. Ceux des routines se lisent dans dandori_list_routines (reminder_time)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the timezone of returned times (UTC), the fact that multiple reminders can map to a single task, and that routine reminders are excluded from this result set.

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 compact sentences with no filler: the first defines scope and result shape, the second handles the sibling boundary. Front-loaded with the most important information (what and how far ahead).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only listing tool with no output schema, the description supplies everything needed: the time window, the returned fields, the UTC convention, the cardinality caveat, and where routine reminders live instead.

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?

There are zero input parameters, so there is nothing for the description to disambiguate. It instead documents the returned fields (reminder time in UTC, task) in the absence of an output schema, which is useful value added.

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 (task reminders), the exact scope (the next three days), and the shape of the result (reminder time in UTC plus task, possibly several per task). It also explicitly carves out routine reminders and points to dandori_list_routines, so an agent can distinguish this tool from the sibling without inspecting either 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 clearly states the window of applicability (three upcoming days) and gives an explicit alternative destination for routine reminders. It does not spell out what to do for reminders beyond three days or other time ranges, but the routing guidance for the main ambiguity is present.

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