Skip to main content
Glama

Class-free days

get_class_free_days
Read-only

List the class's days and lesson ranges without classes, such as holidays and school free days. type_id is an opaque code, not a name; a day without lesson numbers is not necessarily free all day.

Instructions

List the class's days and lesson ranges without classes, such as holidays and school free days. type_id is an opaque code, not a name; a day without lesson numbers is not necessarily free all day.

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_class_free_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items in this page.
cursorNonext_cursor from the previous page; omit for the first page.
account_aliasYesLogin alias from list_accounts.

Output Schema

NameRequiredDescriptionDefault
itemsYes
identityYes
paginationYes
observationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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})?$"
  2. Changed3 schema fields changedv2.5.0
    • removedOutput schema / $defs / PresentationCursor / additionalProperties
      Removed value: -false
    • removedOutput schema / $defs / WindowPagination / additionalProperties
      Removed value: -false
    • removedOutput schema / additionalProperties
      Removed value: -false
  3. Changed4 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 / 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."
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely non-obvious behavioral context: type_id is an opaque code rather than a human-readable name, and a day lacking lesson numbers is not automatically free all day, which warns against an incorrect interpretation of results.

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?

Two sentences with zero filler, leading with what the tool returns and following with the two interpretive caveats an agent actually needs. Nothing is repeated from the schema or annotations.

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 and safety covered by annotations, the description only needs to convey purpose and interpretation pitfalls, which it does. Pagination and account selection are handled by the heavily described schema, so the remaining gap is minor.

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 in the schema; the description adds nothing about them. The type_id remark appears to concern returned data rather than any input parameter, so it does not deepen input semantics.

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?

The description uses a clear verb and resource ('List the class's days and lesson ranges without classes') and illustrates with concrete examples (holidays, school free days). It is distinguishable from get_agenda/get_timetable by being about the complement of scheduled lessons, though it never names an alternative tool to make the contrast explicit.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer this is the tool for holiday/free-day information, but there is no statement of when to prefer it over get_agenda or get_timetable, nor any prerequisite or exclusion. Adequate but leaves the routing decision to inference.

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