Skip to main content
Glama

Schoolwise

Find covered schools

find_school
Read-only

Find covered schools by name or town; a name can match several schools. Omit name to list every covered school (up to 50). 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_school"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo

Output Schema

NameRequiredDescriptionDefault
schoolNo
statusYes
messageNo
schoolsNo
pageDateNo
timezoneNo
candidatesNo
schoolPageUrlNo
calendarCoverageNo
requestSchoolUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, closed-world), yet the description adds real context: the geographic and data-source coverage boundary, the 50-result cap, and the caveat that a name query can be ambiguous. The trailing note about events spanning ~2 weeks and lunch possibly being empty is relevant to planning but describes sibling data rather than this tool's own behavior.

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?

Front-loaded with purpose and the key usage rule, then scope caveats. It is dense but every clause carries information; only the final events/lunch remark is arguably tangential to a school-lookup tool and could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 no explanation. For a single-optional-parameter lookup tool, the description supplies coverage scope, result cap, ambiguity warning, and omission behavior — everything an agent needs to invoke it correctly.

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?

With 0% schema description coverage the description must carry the parameter meaning, and it does: it explains that the single 'name' field also accepts a town, that it is optional, what happens when omitted (full list, capped at 50), and that matches are non-unique. It does not clarify matching semantics (prefix vs substring, case sensitivity), which would have closed the gap fully.

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?

Specific verb+resource: 'Find covered schools by name or town', with the useful clarification that one name may match several schools. It also defines the corpus ('covered schools only: today, schools in Greenwich, Connecticut that have a Schoolwise school page'), which cleanly separates it from the per-school detail siblings, though it never names those siblings explicitly.

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?

Gives a concrete usage rule for the optional parameter: 'Omit name to list every covered school (up to 50)', plus scope constraints (this school year only). However, it never states when to reach for this tool versus get_school_events / get_school_lunch / get_school_days_off; the routing is left implicit.

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