Librus MCP Server

School year archive

get_school_year_archive

Read-only

List earlier school years with marks, behaviour, and achievements for a Librus account, using pagination to review archived records.

Instructions

List earlier school years with their marks and behaviour, then achievements. Cells keep Librus's exact text; a year's year_end mark may differ from that year's annual grade. Each page rereads the archive.

Input Schema

Name	Required	Description
`limit`	No	Maximum items in this page.
`cursor`	No	next_cursor from the previous page; omit for the first page.
`account_alias`	Yes	Login alias from list_accounts.

Output Schema

Name	Required	Description	Default
`items`	Yes
`identity`	Yes
`pagination`	Yes
`observation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv2.5.0Oct 29, 2026
- removedOutput schema / $defs / ArchiveAchievementItem / additionalProperties
```
Removed value: -false
```
- removedOutput schema / $defs / ArchiveYearItem / additionalProperties
```
Removed value: -false
```
- removedOutput schema / $defs / PresentationCursor / additionalProperties
```
Removed value: -false
```
- removedOutput schema / $defs / WindowPagination / additionalProperties
```
Removed value: -false
```
- removedOutput schema / additionalProperties
```
Removed value: -false
```

Changed4 schema fields changedv2.3.1Oct 27, 2026

addedInput schema / properties / account_alias / description
```
Added value: +"Login alias from list_accounts."
```

changedInput schema / properties / account_alias / pattern

Previous value: -"^(?:[^\\s\\x00-\\x1f\\x7f]|[^\\s\\x00-\\x1f\\x7f](?:[^\\s\\x00-\\x1f\\x7f]| )*[^\\s\\x00-\\x1f\\x7f])$"New value: +"^[^\\s\\x00-\\x1f\\x7f](?: *[^\\s\\x00-\\x1f\\x7f])*$"

addedInput schema / properties / cursor / description

Added value: +"next_cursor from the previous page; omit for the first page."

addedInput schema / properties / limit / description
```
Added value: +"Maximum items in this page."
```

First observedOct 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description goes further by warning that cell text is returned verbatim and that a year's year_end mark can legitimately differ from that year's annual grade. 'Each page rereads the archive' hints that pages are not a stable snapshot, though it is too terse to be an actionable caveat.

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 short sentences that front-load what is returned before the caveats, with no filler. The pagination sentence is compressed to the point of ambiguity, costing a little clarity for its brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A read-only list tool with a full output schema, fully documented parameters and annotations covering safety; the description supplies exactly the domain nuance an agent needs (verbatim cells, year_end vs annual grade) so nothing material is missing.

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%, with limit, cursor and account_alias each documented inline, so the baseline is 3. The line 'Each page rereads the archive' gestures at cursor pagination behavior but adds no syntax or format detail beyond the schema's own cursor description.

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?

Names a specific verb and resource: lists earlier (archived) school years with marks, behaviour and achievements, which differentiates it from the current-term grade tools by scope. It stops short of explicitly stating 'not for the current year – use get_grades for that', so the sibling boundary is inferred rather than declared.

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?

The phrase 'earlier school years' plus 'archive' implies the historical-lookup use case, but there is no explicit when-to-use instruction, no prerequisite (e.g. that account_alias comes from list_accounts), and no named alternative such as get_final_grades for the active year.

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