Skip to main content
Glama

Absence justifications

get_justifications
Read-only

List absence justifications parents sent via e-usprawiedliwienia, in Librus's order, with status sent, justified or rejected and decided_by. Covers only date_from..date_to, the window Librus shows by default; older entries are omitted.

Instructions

List absence justifications parents sent via e-usprawiedliwienia, in Librus's order, with status sent, justified or rejected and decided_by. Covers only date_from..date_to, the window Librus shows by default; older entries are omitted. Parent logins only; a student login returns UNSUPPORTED_CAPABILITY. Changes no filter Librus remembers; each page rereads the list.

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": {
      "account_alias": "<account_alias>"
    },
    "name": "get_justifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items in this page.
cursorNonext_cursor from the previous page; omit for the first page.
account_aliasYesLogin alias from list_accounts.

Output Schema

NameRequiredDescriptionDefault
itemsYes
date_toYes
identityYes
date_fromYes
paginationYes
observationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.1

TDQS

A4.1/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint it discloses ordering (Librus's own order), that the result is a bounded window rather than full history, that student credentials hard-fail with UNSUPPORTED_CAPABILITY, and that it mutates no persisted Librus filter. The note that 'each page rereads the list' warns the caller that pages are not a stable snapshot — exactly the kind of trait annotations cannot express.

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?

Three tight sentences, front-loaded with what the tool returns, then scope, then auth and side-effect notes. Every clause carries information; the only friction is the unexplained date_from..date_to reference that has no matching parameter.

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 shape need not be spelled out, and the description covers auth, ordering, windowing and side effects. The remaining gap is that the default window's actual bounds are never stated, so an agent cannot tell whether older records are reachable at all or via another tool.

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 description coverage is 100%, so account_alias, limit and cursor are already documented; the description adds only indirect meaning via 'each page rereads the list' for cursor-based paging. It also references 'date_from..date_to', which are not parameters in the schema, leaving the agent to guess whether that window is implicit or controllable — a small source of confusion rather than added semantics.

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 ('List absence justifications parents sent via e-usprawiedliwienia') and even enumerates the returned status values (sent, justified, rejected, decided_by). The resource is distinct from every sibling (attendance, grades, messages), but the description never explicitly contrasts itself with any alternative, so it stops short of 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 Guidelines4/5

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

Gives a clear eligibility rule ('Parent logins only; a student login returns UNSUPPORTED_CAPABILITY') and a scope condition (only the date_from..date_to window; older entries omitted). There is no explicit when-to-use-instead-of-X routing, but no sibling plausibly overlaps, so the guidance is adequate for selection.

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