Librus MCP Server

Teacher subjects

get_teacher_subjects

Read-only

Lists teachers and the subjects they teach for a Librus account, so you can identify who teaches which subject.

Instructions

Modern accounts: list teachers with the subjects they teach. The IDs are informational and cannot address a message; use get_recipients for that.

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.

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

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

Behavior3/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 usefully adds that the returned IDs are informational and not usable as message recipients, which is real behavioral context. It says nothing about paging behavior or what a 'Modern accounts' restriction implies for accounts outside that set, leaving the main behavioral ambiguity undocumented.

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 short sentences with the core purpose front-loaded and the disambiguation second. The 'Modern accounts:' lead-in is terse to the point of being cryptic, but nothing is wasted.

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

Completeness3/5

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

An output schema exists and pagination is fully described in the schema, so the description needn't cover return values. The remaining gap is the unexplained account-type gating, which leaves an agent unsure whether empty results mean 'no teachers' or 'not a modern account'.

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%, so limit, cursor, and account_alias are already documented inline (including 'next_cursor from the previous page'). The description adds nothing about parameter meaning, which is acceptable at full schema coverage but earns only the baseline.

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?

States a specific verb and resource: 'list teachers with the subjects they teach', which is concrete and distinguishable from the messaging siblings. The unexplained 'Modern accounts:' qualifier slightly muddies the scope, since it implies some accounts are excluded without saying what happens then.

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?

Explicitly routes the agent away from this tool for a plausible-but-wrong use case: the IDs 'cannot address a message; use get_recipients for that.' It stops short of saying when this tool should be used instead (e.g., to discover teacher IDs for other lookups), but the negative guidance is clear and actionable.

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