Skip to main content
Glama

Compare selective schools

compare_schools
Read-onlyIdempotent

Side by side published admissions facts for two to four selective high schools or colleges: rates, counts, requirements, deadlines and cost, each with its source and date. Best with schools of the same kind (two boarding schools, or two colleges). Names that match no school or several schools are listed as unresolved.

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": {
      "schools": "<schools>"
    },
    "name": "compare_schools"
  }
}

Input Schema

NameRequiredDescriptionDefault
schoolsYesTwo to four school names, e.g. ["Exeter", "Andover"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavioral context: every fact carries its source and date (provenance), and non-matching or multi-matching names are reported as unresolved rather than failing silently. It does not say whether the call errors, how much data is returned, or how ambiguity is resolved among the listed candidates.

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?

Three short sentences, front-loaded with the operation and scope, then a usage recommendation, then the failure-mode note. No filler, no restatement of the name or title, and each sentence carries distinct information.

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?

No output schema exists, yet the description effectively describes the return content (the specific fact categories plus per-fact source and date) and how unresolvable names surface. With annotations covering the safety profile and the single parameter fully specified in schema, an agent has everything needed to decide and call 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?

Schema coverage is 100% and the single array parameter is already documented with bounds and an example, so baseline would be 3. The description still adds meaning beyond the schema: the intent of the 2–4 range (comparison across schools) and the recommendation that entries be of the same kind, which the schema cannot express.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific operation (side-by-side comparison) on a specific resource (published admissions facts for selective high schools/colleges), and enumerates the data dimensions returned: rates, counts, requirements, deadlines, cost. The 'two to four schools' scope immediately separates it from a single-school lookup like school_admissions without needing to name it.

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?

Gives a clear usage condition — 'Best with schools of the same kind (two boarding schools, or two colleges)' — which tells the agent when results will be most meaningful, plus the edge case that unmatched or ambiguous names come back as unresolved. It stops short of naming an alternative tool for single-school lookups or for schools of mixed type, so it is clear context rather than explicit routing.

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