Librus MCP Server

Grades by date

get_grades_window

List grades and formative assessments within an inclusive date range for a Librus account, excluding averages and supporting pagination.

Instructions

List grades and formative assessments dated within date_from..date_to, without averages (see get_grades). scope also changes the view this login's Librus session remembers and may not apply to formative rows. A grade whose formative_id equals a formative row's assessment.detail_id is one assessment.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum items in this page.
`scope`	No	Librus view: all, or its week or last_login recent-changes filter; not dates.	all
`cursor`	No	next_cursor from the previous page; omit for the first page.
`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
`scope`	Yes
`date_to`	Yes
`identity`	Yes
`date_from`	Yes
`pagination`	Yes
`observation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 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 / 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."

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

addedInput schema / properties / scope / description

Added value: +"Librus view: all, or its week or last_login recent-changes filter; not dates."

First observedOct 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description adds useful behavior beyond the annotations: scope changes the Librus session's remembered view and may not apply to formative rows. This explains a stateful side effect that aligns with the non-read-only annotation, though it does not discuss permissions, rate limits, or pagination behavior.

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 description is front-loaded with the core purpose and avoids filler. The second sentence about scope and formative rows is somewhat dense, but every sentence carries relevant operational information.

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?

Given the output schema and detailed input schema, the description is largely complete: it covers date filtering, the sibling relationship, scope behavior, and formative identity. Minor gaps around pagination or account context are handled by the schema.

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 100%, so the parameters are already documented. The description still adds meaning by explaining the date range, the session-affecting caveat for scope, and the formative_id/detail_id relationship for identifying assessments.

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?

The description gives a specific verb and resource: 'List grades and formative assessments dated within date_from..date_to.' It also distinguishes this tool from get_grades by noting it returns results 'without averages,' so an agent can select it without guessing.

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?

The date-window use case is clear, and the parenthetical '(see get_grades)' points to the alternative for averages. However, it does not explicitly state when to prefer this tool versus get_grades beyond that single contrast, so it falls short of full when/when-not guidance.

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