Skip to main content
Glama

Compare colleges

compare
Read-onlyIdempotent

Compare 2 to 4 colleges side by side: admit rates by round, SAT/ACT ranges, testing policy, sticker cost, average net price, graduation rate, size and setting. If GPA or scores are given, adds the student's estimated odds (same model as prefrosh.ai/chance).

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

Input Schema

NameRequiredDescriptionDefault
actNoBest ACT composite.
gpaNoUnweighted GPA, ideally on a 4.0 scale (a 100-point average also works).
satNoBest total SAT (superscore is fine).
schoolsYes
home_stateNoTwo-letter US state the student lives in (matters for public universities).

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 establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description adds useful context that the comparison is capped at 2-4 schools and that odds come from the same model as prefrosh.ai/chance. It omits failure behavior, such as what happens with an unrecognized school name.

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?

Two dense sentences with the core comparison scope front-loaded and the optional odds behavior second; no filler or repetition of annotation facts.

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?

With no output schema, the description does the necessary work of enumerating returned fields, and it explains the optional student-stat path. The remaining parameter (home_state) is adequately covered by its own schema description.

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 80%, so the schema already documents most parameters. The description adds meaning beyond the schema by explaining the causal effect of gpa/sat/act (they trigger the added odds estimate) rather than merely restating their formats.

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?

Names a specific verb and resource (compare colleges side by side) and enumerates exactly what is compared: admit rates by round, test ranges, cost, graduation rate, size/setting. This clearly separates it from single-school siblings like school_card and my_odds.

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 clear context on when the odds extension applies ('If GPA or scores are given, adds the student's estimated odds'), which tells the agent the stats parameters are optional. It does not, however, explicitly exclude cases or point to siblings such as school_card for one school or my_odds for a single-chance calculation.

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