Skip to main content
Glama

Homework

get_homework

Lists homework within a date range, defaulting to today through 14 days ahead in Warsaw time, with paging for long ranges and item references for detail lookups.

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. Long ranges are paged; pass pagination.next_cursor with the returned date_from and date_to for the rest. The range also changes what this login's Librus session remembers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account_alias": "<account_alias>"
    },
    "name": "get_homework"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items in this page.
cursorNonext_cursor from the previous page; omit for the first page.
date_toNoLast day, YYYY-MM-DD, inclusive; at most 370 days after the first.
date_fromNoFirst day, YYYY-MM-DD, inclusive.
account_aliasYesLogin alias from list_accounts.

Output Schema

NameRequiredDescriptionDefault
itemsYes
date_toYes
identityYes
date_fromYes
paginationYes
observationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.9.0
    • addedInput schema / $defs
      Added value: +{
      +  "PresentationCursor": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "context": {
      +        "pattern": "^[0-9a-f]{64}$",
      +        "type": "string"
      +      },
      +      "offset": {
      +        "maximum": 4096,
      +        "minimum": 1,
      +        "type": "integer"
      +      },
      +      "query": {
      +        "pattern": "^[0-9a-f]{64}$",
      +        "type": "string"
      +      },
      +      "source": {
      +        "pattern": "^[0-9a-f]{64}$",
      +        "type": "string"
      +      },
      +      "version": {
      +        "const": 1,
      +        "default": 1,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "context",
      +      "query",
      +      "source",
      +      "offset"
      +    ],
      +    "type": "object"
      +  }
      +}
    • addedInput schema / properties / cursor
      Added value: +{
      +  "anyOf": [
      +    {
      +      "$ref": "#/$defs/PresentationCursor"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "next_cursor from the previous page; omit for the first page."
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 256,
      +  "description": "Maximum items in this page.",
      +  "maximum": 256,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedOutput schema / $defs / Pagination
      Removed value: -{
      -  "properties": {
      -    "consistency": {
      -      "const": "best_effort",
      -      "default": "best_effort",
      -      "type": "string"
      -    },
      -    "next_cursor": {
      -      "default": null,
      -      "type": "null"
      -    },
      -    "truncated": {
      -      "const": false,
      -      "default": false,
      -      "type": "boolean"
      -    }
      -  },
      -  "type": "object"
      -}
    • addedOutput schema / $defs / PresentationCursor
      Added value: +{
      +  "properties": {
      +    "context": {
      +      "pattern": "^[0-9a-f]{64}$",
      +      "type": "string"
      +    },
      +    "offset": {
      +      "maximum": 4096,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    "query": {
      +      "pattern": "^[0-9a-f]{64}$",
      +      "type": "string"
      +    },
      +    "source": {
      +      "pattern": "^[0-9a-f]{64}$",
      +      "type": "string"
      +    },
      +    "version": {
      +      "const": 1,
      +      "default": 1,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "context",
      +    "query",
      +    "source",
      +    "offset"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / $defs / SizedWindowPagination
      Added value: +{
      +  "properties": {
      +    "consistency": {
      +      "const": "best_effort",
      +      "default": "best_effort",
      +      "type": "string"
      +    },
      +    "next_cursor": {
      +      "anyOf": [
      +        {
      +          "$ref": "#/$defs/PresentationCursor"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "reason": {
      +      "anyOf": [
      +        {
      +          "enum": [
      +            "item_limit",
      +            "size_limit"
      +          ],
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "truncated": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "next_cursor",
      +    "truncated",
      +    "reason"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / properties / pagination / $ref
      Previous value: -"#/$defs/Pagination"New value: +"#/$defs/SizedWindowPagination"
    • changedOutput schema / required
      Previous value: -[
      -  "items",
      -  "identity",
      -  "observation",
      -  "date_from",
      -  "date_to"
      -]New value: +[
      +  "items",
      +  "identity",
      +  "observation",
      +  "pagination",
      +  "date_from",
      +  "date_to"
      +]
  2. Changed1 schema field changedv2.8.1
    • changedOutput schema / $defs / Observation / properties / observed_at / pattern
      Previous value: -"^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(?:\\.[0-9]{1,6})?(?:Z|[+-][0-9]{2}:[0-9]{2})?$"New value: +"^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(\\.[0-9]{1,6})?(Z|[+-][0-9]{2}:[0-9]{2})?$"
  3. Changed4 schema fields changedv2.5.0
    • removedOutput schema / $defs / HomeworkItemOutput / additionalProperties
      Removed value: -false
    • removedOutput schema / $defs / Pagination / additionalProperties
      Removed value: -false
    • removedOutput schema / $defs / SchoolReferenceInput / additionalProperties
      Removed value: -false
    • removedOutput schema / additionalProperties
      Removed value: -false
  4. Changed5 schema fields changedv2.3.1
    • 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])*$"
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description explains the otherwise puzzling readOnlyHint=false: the requested range mutates what the login's Librus session remembers. It also discloses paging behaviour for long ranges and the exact cursor round-trip (next_cursor plus the returned date_from/date_to), which annotations do not convey.

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 dense sentences, front-loaded with the core action and date rule, then routing, then paging and session side effects. The session-remembers sentence is slightly oblique, but nothing is redundant.

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 not be explained, and the description covers defaults, timezone, paging and the session side effect. It leaves only minor gaps, such as whether results are scoped per account_alias or span all children on the login.

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, but the description adds real constraint knowledge the schema lacks: the both-or-neither rule for date_from/date_to, the implied default window, the timezone, and how cursor must be paired with the returned dates.

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?

"List homework in a date range" gives a specific verb (list) plus resource (homework) plus scope (date range), and it explicitly routes item-level lookups to get_homework_detail, so it is distinguishable from its sibling 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?

It states the selection rule precisely: supply both dates or neither, and describes the default window (today to 14 days ahead, Warsaw time). It also names the alternative (get_homework_detail) and the condition that selects it (having an item's reference).

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