Skip to main content
Glama

Schoolwise

School lunch

get_school_lunch
Read-only

Use to ask what the school page lists for lunch. An empty list means the page lists none. 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_lunch"
  }
}

Input Schema

NameRequiredDescriptionDefault
schoolYes

Output Schema

NameRequiredDescriptionDefault
schoolNo
statusYes
lunchesNo
messageNo
pageDateNo
timezoneNo
candidatesNo
hasLunchDataNo
schoolPageUrlNo
calendarCoverageNo
requestSchoolUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare a safe read-only, non-destructive, closed-world operation. The description adds meaningful behavior: an empty list means no lunch entries, coverage is limited to today and to specific schools, and results can be empty even within scope.

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 key behavior and constraints are front-loaded in a few short sentences with little wasted wording. Some phrasing, especially the events coverage note, is terse and slightly ambiguous.

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, so the description need not explain the return shape. It covers scope and empty-result behavior well, but leaves the accepted school identifier format unclear, which matters for invoking this one-parameter tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required schema parameter with no description coverage. The description implies that 'school' refers to a covered Schoolwise school, but it does not say whether the value should be a school name, an ID, or another identifier, so it does not compensate for the schema gap.

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 verb and resource: asking what the school page lists for lunch. It also mentions that the result is an empty list when none are listed. It does not explicitly say how this differs from get_school_events or get_school_days_off, though it hints at event windows.

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?

It gives clear usage constraints: today only, Greenwich Connecticut schools with a Schoolwise page, and the current school year. It notes that events cover about the next two weeks and lunch can be empty. It stops short of naming the sibling tools to use for events or days off.

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