Skip to main content
Glama

Supprimer Calendrier

supprimer_calendrier

Removes an imported calendar by its identifier. Use it to delete a calendar from Evento when you have the ID returned by the calendar listing tool.

Instructions

Retire un calendrier importé (identifiant fourni par lister_calendriers).

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": {
      "calendrier_id": "<calendrier_id>"
    },
    "name": "supprimer_calendrier"
  }
}

Input Schema

NameRequiredDescriptionDefault
calendrier_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a meaningful eligibility constraint (only imported calendars) and the provenance of the identifier, but says nothing about irreversibility, required permissions, or side effects on related polls — critical for a destructive operation.

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?

One short sentence, front-loaded with the action and resource, with zero filler. It is efficient for a low-complexity tool, though the same brevity leaves behavioral gaps rather than wasting words.

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 the tool takes only one required parameter. Still, for an unannotated destructive operation the description should address reversibility and permissions; those omissions keep it at minimum viable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single parameter, so the description must compensate. It does add real value by telling the agent where the calendrier_id comes from (lister_calendriers), but it gives no type or format detail beyond the schema's integer declaration.

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 ('Retire un calendrier importé'), which an agent can distinguish from listing/adding siblings. It does not explicitly contrast with any other deletion tool, but the 'importé' qualifier narrows the target clearly.

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 rather than spelled out: the tool applies to imported calendars only, and the identifier must come from lister_calendriers. There is no explicit when-not guidance or statement about what happens to dependent data, leaving the agent to infer preconditions.

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