Skip to main content
Glama

Selective school admissions facts

school_admissions
Read-onlyIdempotent

Published admissions facts for one selective school: magnet and boarding high schools (for example Phillips Exeter, Stuyvesant, NCSSM, Lawrenceville) and selective colleges (for example MIT, Yale, UVA). Returns admission rates and counts, application requirements, deadlines, cost and aid facts, each with its source and the date EduAvenues checked it, plus a link to the free EduAvenues school guide. If the name matches more than one school, returns the candidates to choose from. For TJHSST, use tj_admissions_facts.

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": "school_admissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
schoolYesSchool name or common short name, e.g. "Exeter", "Stuyvesant", "MIT"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent lookup. The description adds meaningful behavior beyond that by listing returned facts, source/check dates, guide links, and the candidate-list fallback for ambiguous school names.

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 description is front-loaded and informative, with examples that help scope the tool. It is somewhat dense but does not contain obvious filler.

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?

For a simple one-parameter lookup without an output schema, the description explains the return contents, source transparency, ambiguity handling, and sibling alternative. It could be slightly more complete by mentioning no-match behavior, but overall it is sufficient.

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 coverage is 100% for the single school parameter, so the schema already documents the input fully. The description adds only a little beyond that by noting that a name can match multiple schools and then return candidates.

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?

The description uses a specific verb and resource: published admissions facts for one selective school. It clearly scopes coverage to selective high schools and colleges, and explicitly distinguishes itself from tj_admissions_facts.

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 context for selective schools and names the alternative tool for TJHSST. It does not explicitly state what to do for non-selective schools or no-match cases, but the scope is otherwise clear.

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