Skip to main content
Glama

Schoolwise

Coming school events

get_school_events
Read-only

Use for up to 10 events on the school page, optionally for one of the school's grades. Later events are marked; no class or teacher view. 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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
gradeNo
schoolYes

Output Schema

NameRequiredDescriptionDefault
eventsNo
schoolNo
statusYes
messageNo
pageDateNo
timezoneNo
candidatesNo
schoolPageUrlNo
calendarCoverageNo
requestSchoolUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 a safe, closed-world read, so the description wisely spends its space on operational traits: a hard cap of 10 results, that later events are flagged, the geographic and school-page coverage limits, and the roughly two-week horizon. The closing phrase 'lunch can be empty' is opaque and unclear whether it refers to an empty result set or a lunch field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loading with 'Use for' is good and the coverage constraints earn their place, but the text is telegraphic, packing several unrelated caveats into one run-on block. The trailing 'lunch can be empty' clause is unexplained and reads as a stray fragment.

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 shape need not be described, and annotations cover the safety profile. Given that, the description supplies the domain limits an agent needs (coverage area, school-page requirement, time window, result cap); only the dual-typed grade parameter remains under-explained.

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 0%, so the description must carry the load. It clarifies that 'grade' is optional and refers to one of the school's own grades, and that 'school' must be a covered school, but it never explains that grade accepts either a name string or a 0-20 integer, leaving a real ambiguity in the schema.

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: retrieve up to 10 upcoming events from a school page, optionally narrowed to one grade. It also excludes class/teacher-level views, which helps separate it from the other school tools, though it never names a sibling explicitly.

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?

Opens with 'Use for...' and scopes the use case with concrete eligibility conditions (Greenwich, Connecticut schools with a Schoolwise page, current school year, roughly the next two weeks). It gives exclusions ('no class or teacher view') but no explicit pointer to get_school_lunch or get_school_days_off for adjacent data.

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