Skip to main content
Glama

College card

school_card
Read-onlyIdempotent

Show one college as a card: photo or campus map, overall admit rate and admit rate by round (Early Decision, Early Action, Regular Decision) with deadlines, SAT/ACT middle 50%, testing policy, sticker cost, average net price, graduation rate, biggest majors, and a link to its prefrosh.ai page. Use for "tell me about X", "how hard is it to get into X", "what are X's deadlines". Data is from the school's Common Data Set and federal data; cite the prefrosh.ai URL in the result.

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

Input Schema

NameRequiredDescriptionDefault
schoolYesCollege name as the user wrote it, e.g. "Tufts", "UNC", "Wash U".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so safety is covered. The description adds real behaviour beyond that: data provenance (Common Data Set plus federal data) and an explicit obligation to cite the prefrosh.ai URL in the response, which an agent would otherwise not know. It stops short of saying what happens on an ambiguous or unmatched 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded and the sentence packs trigger phrases and provenance without filler. It is one very long sentence, though, and the field inventory is dense enough that a reader can lose the action statement mid-clause; light splitting would improve scannability.

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 carries the full burden of describing the return value, and it does so exhaustively — media, per-round admit rates with deadlines, test ranges, policy, costs, outcomes, majors and link. Provenance and citation duty round it out, leaving nothing an agent needs before calling.

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?

The single parameter is fully documented in the schema, including the 'as the user wrote it' convention and nickname examples, so the description does not need to carry it. The description adds nothing parameter-specific beyond implying a single school per call. Baseline 3 is appropriate at 100% schema coverage.

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?

A specific verb plus resource ('Show one college as a card') followed by an explicit inventory of what the card contains (admit rates by round, SAT/ACT middle 50%, net price, graduation rate, majors). That scope is clearly singular-school, which separates it from the sibling tools compare and my_odds without the agent opening any schema.

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 names three concrete user phrasings that should trigger the tool ("tell me about X", "how hard is it to get into X", "what are X's deadlines"), which is strong positive routing. It never states when not to use it, though — most obviously that multiple schools should go to compare, and that my_odds covers chance-me calculation — so the exclusion side is left 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