Skip to main content
Glama

QRavate QR codes

Programmer un changement

schedule_destination_change
Destructive

Programme un changement de destination à une date donnée (ISO 8601, par exemple 2026-06-21T08:00:00+02:00), appliqué dans le quart d’heure suivant. À partir du plan Essentiel. Nécessite l’accès en écriture.

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": {
      "qr": "<qr>",
      "run_at": "<run_at>",
      "destination": "<destination>"
    },
    "name": "schedule_destination_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
qrYes
run_atYes
destinationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag a destructive, non-idempotent write, and the description adds genuinely new behavior: execution is not exact but lands within the quarter hour following run_at, plus plan and permission gates. It does not say whether a new schedule replaces or stacks on an existing one, which matters for a destructive non-idempotent call.

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?

A single dense sentence with the action, the format example, the execution window, and the two gates, all front-loaded. Nothing is wasted, though the parenthetical example slightly interrupts the flow.

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?

Covers timing semantics, format, plan, and auth for a destructive mutation with no output schema. Still missing what 'qr' identifies, whether scheduling is replace-or-append, and whether a scheduled change can be inspected or cancelled afterward.

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%, so the description must carry the load; it does explain run_at's ISO 8601 format with a concrete offset example, which is the highest-risk parameter. The 'qr' and 'destination' parameters get no explanation beyond the schema's uri format, leaving the identifier semantics undocumented.

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 ('Programme un changement de destination') plus the scheduling dimension, which separates it from an immediate update. It does not name the sibling update_destination, so the agent must infer the distinction from the name alone.

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?

Gives real prerequisites — requires the Essentiel plan and write access — which tells the agent when the call is even permissible. It never states when to prefer this over an immediate destination update, nor what happens if a change is already scheduled.

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