Skip to main content
Glama

Selective admissions calendar

application_calendar
Read-onlyIdempotent

Upcoming published application dates (open houses, applications, tests, decisions) for selective high schools, TJHSST and selective colleges, in date order with the source for each. Give school names to narrow it, or none for every school EduAvenues covers. College application deadlines are listed by plan (Early Decision, Early Action, Regular Decision).

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

Input Schema

NameRequiredDescriptionDefault
fromNoShow dates on or after this day, YYYY-MM-DD (default today)
limitNoHow many dates to return (default 20)
schoolsNoSchool names to include (default every covered school)

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 establish that this is a safe, idempotent, closed-world read, so the safety profile needs no restating. The description adds genuine behavior beyond that: only *published* dates are returned, results are date-ordered with a source per entry, and college deadlines are grouped by admission plan. What it omits is truncation/limit behavior — nothing says the list may be cut off at the limit and how an agent would know results were capped.

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 sentences, each earning its place: the first states the resource, scope, ordering, and source attribution; the second covers the only optional filter; the third covers a notable result-shape detail. Scope and defaults are front-loaded with no filler or repetition of the title.

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?

With no output schema, the description carries the burden of describing returns, and it does so adequately: date order, per-entry source, and plan-grouped college deadlines. The only real gap is the lack of any statement about result capping or coverage boundaries for a zero-required-parameter tool that defaults to all schools.

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 100%, so the schema already documents `from`, `limit`, and `schools` including their defaults, so the baseline is 3. The description reinforces the `schools` default ("none for every school") but adds no date-format, range, or limit semantics beyond what the schema states, and the admission-plan sentence describes returned content rather than a parameter.

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 names a concrete resource (published application dates for open houses, applications, tests, decisions) and a concrete population (selective high schools, TJHSST, selective colleges), plus the output ordering and per-row source attribution. It is clearly distinguishable from siblings like school_admissions or tj_admissions_facts, though it never explicitly contrasts itself with them.

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?

"Give school names to narrow it, or none for every school EduAvenues covers" tells the agent how to scope the query, which implies the broad-scan vs. targeted-lookup usage. However, there is no when-not guidance, no statement of prerequisites, and no named alternative for questions this tool does not answer (e.g. admissions statistics), leaving routing to inference.

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