Skip to main content
Glama

TJHSST admissions facts

tj_admissions_facts
Read-onlyIdempotent

Official TJHSST (Thomas Jefferson High School for Science and Technology) admissions facts from FCPS data EduAvenues obtained, including FOIA responses not published elsewhere: admission rates by middle school, class year, gender, race/ethnicity and experience factors (economically disadvantaged, multilingual learners, students with disabilities), average GPA of admitted, waitpooled and rejected applicants, and the 2026-27 application and test dates. Use view "overview" for the big picture and dates, "middle_school" with a school name, or "class_year" with a year (2025-2029). Rates only, each with its source and received date; suppressed groups are marked.

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

Input Schema

NameRequiredDescriptionDefault
viewNoWhich facts to return (default overview)
classYearNoTJ graduating class year for view "class_year"
middleSchoolNoMiddle school name for view "middle_school", e.g. "Carson"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine output context beyond them: results are 'rates only', each carries its source and received date, and suppressed groups are marked — important for interpreting gaps. It does not describe pagination or failure behavior, so it is useful but not rich.

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 the resource and provenance, then view routing, then a short caveat sentence. Dense but every clause carries information; the long enumerations in the first sentence could be tightened slightly.

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?

No output schema exists, so the description correctly spends effort describing what comes back (rates, source, received date, suppressed-group markers). Combined with the annotated read-only nature and full schema coverage, an agent has enough to call this correctly; only return format specifics like exact fields remain unstated.

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 100% schema coverage the baseline would be 3, but the description goes further by binding each view value to the parameter it requires ('middle_school' with a school name, 'class_year' with a year 2025-2029), which clarifies how to combine the optional arguments. It still leaves the default and interaction rules mostly to the schema.

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 resource (official TJHSST admissions facts from FCPS/EduAvenues FOIA data) and enumerates exactly what dimensions are covered: admission rates by middle school, class year, gender, race/ethnicity, experience factors, GPA of admitted/waitpooled/rejected, and 2026-27 dates. The 'FOIA responses not published elsewhere' clause further distinguishes this authoritative dataset from other admissions-style data.

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?

Explicitly routes the caller across its three views: 'overview' for the big picture and dates, 'middle_school' with a school name, 'class_year' with a year (2025-2029). That is clear when-to-use-which guidance, though it offers no guidance on when to prefer this tool over related admissions/calendar siblings or any exclusion conditions.

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