Librus MCP Server

Homework

get_homework

List homework assignments for an account alias within a date range, or omit dates to retrieve today through 14 days ahead in Warsaw time.

Instructions

List homework in a date range; give both dates or neither (today to 14 days ahead, Warsaw time). Pass an item's reference to get_homework_detail. The range also changes what this login's Librus session remembers.

Input Schema

Name	Required	Description
`date_to`	No	Last day, YYYY-MM-DD, inclusive; at most 370 days after the first.
`date_from`	No	First day, YYYY-MM-DD, inclusive.
`account_alias`	Yes	Login alias from list_accounts.

Output Schema

Name	Required	Description	Default
`items`	Yes
`date_to`	Yes
`identity`	Yes
`date_from`	Yes
`pagination`	No
`observation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 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 / date_from / description
```
Added value: +"First day, YYYY-MM-DD, inclusive."
```

addedInput schema / properties / date_to / description

Added value: +"Last day, YYYY-MM-DD, inclusive; at most 370 days after the first."

changedOutput schema / $defs / SchoolReferenceInput / properties / account / 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])*$"

First observedOct 27, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false with destructiveHint=false, which is counterintuitive for a list operation. The description explains why by disclosing the non-obvious side effect: the range alters what the login's Librus session remembers. That is real value beyond the annotations. It stops short of describing errors, rate limits, or what an invalid range does.

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 clauses, front-loaded with purpose, then constraint, then handoff, then the side-effect note. Efficient overall, though the session-memory clause is compressed.

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?

Covers default window, timezone, date pairing, sibling handoff, and the session side effect, which is enough for a 3-param read tool with an output schema. Slightly less than fully complete because error and auth behavior remain unstated.

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 100%, so both date fields and the alias are already documented, setting the baseline at 3. The description adds the pairing constraint and the meaning of the null default, but not much else residual. Baseline 3 fits.

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 ("List homework in a date range") and immediately distinguishes itself from the natural sibling by naming get_homework_detail as the follow-up call. An agent can tell which of the homework tools is the entry point without opening a 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 the concrete rule for the date parameters ("give both dates or neither") and explains how to reach detail records, plus what happens when omitted (today to 14 days ahead, Warsaw time). It doesn't state exclusions or when another sibling (e.g. agenda) would be preferable, so it falls short of a full when/when-not treatment.

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