Librus MCP Server

Attendance

get_attendance

Lists paginated Librus attendance records for a login alias with optional all, week, or last-login view scope. Use for attendance review; use window or frequency tools for date ranges and totals.

Instructions

List attendance records. For a date range use get_attendance_window; for totals use get_attendance_frequency. scope also changes the view this login's Librus session remembers.

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.
`account_alias`	Yes	Login alias from list_accounts.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.5.0Oct 29, 2026
- 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

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."
```

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.4/5.0

Behavior4/5

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

Annotations mark this 'List' operation as readOnlyHint=false, and the description explains why: scope mutates the remembered view in this login's Librus session. That is exactly the kind of side effect structured fields cannot convey. It stops short of describing pagination behavior or rate/scope limits, but the key behavioral surprise is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, zero filler, with the core action front-loaded before the routing hints and the session-state caveat.

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 no explanation, and pagination/cursor details are carried by the schema. Purpose, routing, and the session side effect are all covered; only detail-level sibling routing is missing.

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 baseline is 3, and the description earns a bump by adding meaning beyond the schema: scope is not just a filter, it changes what the Librus session remembers for subsequent calls. That is non-obvious semantics an agent could not infer from the enum description.

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?

Opens with a specific verb+resource ('List attendance records') and immediately names the two sibling tools that cover adjacent purposes (get_attendance_window for date ranges, get_attendance_frequency for totals). An agent can distinguish this from the other attendance tools 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?

Explicit routing is given: date ranges go to get_attendance_window, totals to get_attendance_frequency, implying this tool is the plain listing. Strong, but it omits get_attendance_detail, which is the other close sibling an agent might confuse with a record listing.

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