Skip to main content
Glama

Schoolwise

School days off

get_school_days_off
Read-only

Use for days off and early releases: the school page's remaining school-year calendar plus closures in the next 14 days. Dates use the school's clock; school-wide only. Covered schools only: today, schools in Greenwich, Connecticut that have a Schoolwise school page. This school year only; events cover about the next two weeks, and lunch can be empty.

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": {
      "school": "<school>"
    },
    "name": "get_school_days_off"
  }
}

Input Schema

NameRequiredDescriptionDefault
schoolYes

Output Schema

NameRequiredDescriptionDefault
schoolNo
statusYes
daysOffNo
messageNo
pageDateNo
timezoneNo
candidatesNo
schoolPageUrlNo
calendarCoverageNo
requestSchoolUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/closed-world annotations, the description discloses substantial operational context: coverage is limited to today's schools in Greenwich, Connecticut with a Schoolwise page, results span only the current school year with events about two weeks out, dates follow the school's clock, and lunch can be empty. These are real constraints an agent could otherwise get wrong.

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?

The usage trigger is front-loaded and the remaining clauses are dense but each adds a real constraint (timezone, geography, time window, empty lunch). The semicolon-chained phrasing is slightly run-on but wastes little.

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 annotations covering safety, the description needn't explain return values, and it does supply the coverage and time-window caveats that matter. The remaining gap is the format and resolution path for the required 'school' argument.

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?

The single 'school' parameter has 0% schema description coverage, so the description carries the burden, and it only indirectly constrains values by describing which schools are covered. It never states whether the argument is a name, slug, or ID, nor that find_school should be used to resolve it.

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 states a specific resource and scope: 'days off and early releases' drawn from the school page's remaining school-year calendar plus closures in the next 14 days. It is clearly distinct from a lunch or events lookup ('school-wide only', 'lunch can be empty'), though it never names the sibling tools directly.

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?

'Use for days off and early releases' gives an explicit when-to-use trigger, and 'school-wide only' implicitly excludes per-grade or per-student queries. What is missing is an explicit pointer to an alternative tool (e.g. events or lunch) or a note on obtaining a valid school identifier.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources