Librus MCP Server

Attendance by date

get_attendance_window

Lists attendance records for a specific date range (date_from to date_to) in a Librus account, paged with a cursor. Use it to view attendance across multiple days instead of a single record fetch.

Instructions

List attendance records dated within date_from..date_to. Use this instead of get_attendance for a date range. 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.
`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.

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

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?

Annotations declare readOnlyHint=false and openWorldHint=true, and the description usefully explains why: the scope parameter mutates the remembered Librus session view. That is genuine behavioral context beyond the annotations. It stops short of covering pagination/output behavior, but the cursor and output schema handle that.

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?

Two sentences, front-loaded with the date-range behavior and followed by the sibling routing. The session-view sentence is slightly terse/cryptic but still earns its place by explaining a non-obvious side effect.

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?

With an output schema present, return values need no explanation, and the schema fully documents the six parameters. The description covers purpose, alternative routing, and the key side effect; only minor gaps in phrasing about the session-mutation semantics remain.

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%, including per-parameter descriptions for date_from/date_to, limit, cursor, scope, and account_alias, so the baseline is 3. The description only adds the reminder that scope alters the session view, marginally beyond the schema's own 'not dates' note.

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 attendance records') plus the exact scoping ('dated within date_from..date_to'), and explicitly names the sibling it replaces for range queries. An agent can distinguish it from get_attendance without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly says 'Use this instead of get_attendance for a date range', giving a concrete when-to-use and a named alternative. No inference required.

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