Skip to main content
Glama

journal_evenements

Read-onlyIdempotent

Retrieves alarm and production-line stoppage timelines with each stop's cause and duration, helping diagnose why a line stopped over a chosen period.

Instructions

Chronologie des alarmes et des arrêts de la ligne, avec la cause et la durée de chaque arrêt.

    C'est l'outil à utiliser pour répondre à « pourquoi la ligne s'est-elle arrêtée ? ».

    Args:
        periode: « 30min », « 8h », « 2j » ou « nuit » (22 h → 6 h, la plus récente).
        debut: date ISO 8601 de début (heure locale), prioritaire sur periode.
        fin: date ISO 8601 de fin.
    

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": "journal_evenements"
  }
}

Input Schema

NameRequiredDescriptionDefault
finNo
debutNo
periodeNo24h

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), and the description adds genuine behavioral content: the journal returns cause and duration per stoppage, in chronological order, and 'debut' is interpreted in local time. It does not address result volume, ordering guarantees beyond 'chronologie', or pagination limits.

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?

The core purpose and the motivating question are front-loaded in the first two sentences, and the Args block is compact despite the indentation artifacts. Slight redundancy between 'arrêts' and 'durée de chaque arrêt', but nothing that costs an agent meaningful reading effort.

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?

An output schema exists, so return values need not be described, yet the description still conveys the useful shape of a journal entry. With three optional, undocumented-in-schema parameters, the argument notes are close to sufficient; the only real omission is the interaction/format rules for 'fin'.

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 0%, so the description carries the full burden, and it does document all three parameters: valid periode values with an explicit definition of 'nuit' (22 h → 6 h, most recent), the ISO 8601 local-time format for debut, and debut's precedence over periode. Gaps remain on fin's format, its default, and whether fin can be used without debut.

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?

States a specific verb and resource: a chronological journal of line alarms and stoppages, including cause and duration for each stoppage. That is concrete enough for an agent to distinguish it from a plain alarm list such as lister_alarmes without opening any 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?

Gives an explicit use case in the form of the question it answers ("pourquoi la ligne s'est-elle arrêtée ?"), which tells the agent exactly when to reach for it. It stops short of naming when not to use it or pointing to a sibling alternative, so it is clear context rather than full routing guidance.

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