Skip to main content
Glama

Ajouter Calendrier

ajouter_calendrier

Imports an ICS calendar from an iCal URL, assigning a display name and color to support event scheduling and conflict analysis.

Instructions

Importe un calendrier ICS (URL iCal, souvent un flux secret).

nom : libellé du calendrier ; url : adresse du flux ICS ; couleur : couleur d'affichage au format #rrggbb.

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": {
      "nom": "<nom>",
      "url": "<url>"
    },
    "name": "ajouter_calendrier"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomYes
urlYes
couleurNo#6b79b8

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. "Importe" signals a mutation, but the description does not say whether the URL is fetched immediately, what errors occur on an unreachable/duplicate feed, or whether the operation is idempotent — important gaps for a write tool with zero annotation coverage.

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 compact parts — a one-line purpose followed by a parameter glossary — with no filler. The front-loaded purpose sentence is the most useful content and appears first.

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?

An output schema exists, so return values need not be explained, and parameter meaning is covered. However, for an unannotated mutation tool it omits error/duplicate behavior, auth prerequisites, and whether the feed is validated at import time, leaving meaningful gaps.

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 description coverage is 0%, but the description compensates by defining all three parameters: nom as the calendar label, url as the ICS feed address, and couleur as the display color in #rrggbb format. Only minor gaps remain, such as whether nom must be unique or what the default color means.

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: "Importe un calendrier ICS", adding the clarifying detail that the source is an iCal URL and often a secret feed. This clearly distinguishes it from sibling listing/deleting tools, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus alternatives, no prerequisites (e.g. where to find the ICS URL, permissions needed), and no mention of what happens if the calendar already exists. Only the parenthetical "souvent un flux secret" hints at context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.