Skip to main content
Glama

Calendrier

dandori_calendar
Read-onlyIdempotent

Événements entre deux dates : tâches à échéance, routines, projets, objectifs, contrats, dépenses récurrentes, dates importantes (anniversaires…). Deux ans au plus ; entity_id donne l'ID de l'élément. Une tâche récurrente y montre aussi ses prochaines fois (meta.projected) : elles n'existent pas encore, entity_id est la tâche en cours

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "dandori_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDernier jour inclus (YYYY-MM-DD)
fromYesPremier jour (YYYY-MM-DD)
typesNoTypes à inclure ; par défaut tous
space_idNoNe garder que cet espace pour les tâches, projets, objectifs et dépenses ; routines, contrats et dates importantes restent

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: the two-year maximum window and the fact that projected recurrences in meta.projected do not yet exist and share the current task's entity_id. It stops short of describing ordering, volume or pagination of results.

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?

Dense and front-loaded: scope first, then the range limit, then the entity_id/projected-recurrence caveat. No filler sentences, though the final clause about meta.projected is compressed enough to require a second read.

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 return-value burden and does address the most confusing case (projected recurring occurrences and their entity_id). It omits the general shape of a returned event (fields, sorting, limits), which is a moderate residual gap for an aggregation tool.

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%, so the baseline is 3; the description still contributes the 'two years maximum' constraint on from/to, which the schema does not state. The types enumeration mirrors the schema enum and adds little, and the entity_id note refers to output rather than input.

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 names the resource precisely ('Événements entre deux dates') and enumerates every event type it aggregates (tâches, routines, projets, objectifs, contrats, dépenses récurrentes, dates importantes), so an agent knows exactly what comes back. It does not explicitly contrast itself with sibling tools, which keeps it from 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?

Usage is implied by the date-range framing and bounded by the hard constraint 'Deux ans au plus', but there is no explicit when-to-use / when-not guidance and no named alternative for narrower lookups (e.g. a single task or project fetch). Adequate but with a clear gap.

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