Skip to main content
Glama

The admissions game

admissions_game
Read-only

Run the student's application past prefrosh.ai's simulated admissions committee for one college and round: five fictional readers (first, second, essay and faculty readers, and a dean who chairs) read it, argue, vote (accept / waitlist or defer / deny), and give the top 3 fixes. It is a simulation, not a prediction. Takes about a minute; the room plays out in the view. Pass the student's own application text exactly as they gave it (essays, activities, grades, scores) in "application"; never write, invent or improve content for them. If they have not shared their application, ask them to paste it first.

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>",
      "application": "<application>"
    },
    "name": "admissions_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
majorNoIntended major, if stated.
roundNoApplication round. Default RD.
schoolYesCollege name.
applicationYesThe student's application as they gave it: essays, activities, grades, scores, notes. Verbatim.
visited_campusNoCampus visits, if the student said.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the run takes about a minute, it is a simulation rather than a prediction, the deliberation plays out in the view, and the result includes a decision and three fixes. These latency, fidelity and output-shape details are exactly what the schema and annotations cannot convey.

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 action and scope, then the caveat, then the input rule. It is a little long, but each sentence adds distinct information (scope, fidelity, latency, verbatim rule, prerequisite), with only minor overlap between 'exactly as they gave it' and the schema's verbatim note.

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?

Covers the essentials for a tool with no output schema: what it returns (vote, top 3 fixes), how long it takes and what input is required. It does not say how the agent should subsequently use the siblings game_read, game_vote or game_debrief on the running simulation, which is the one meaningful gap.

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 already 100%, so the baseline is 3. The description adds a real constraint on the application parameter, requiring the student's own text verbatim and forbidding the agent from writing, inventing or improving content, which goes beyond the schema's 'Verbatim' note.

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 concrete verb and resource: run the student's application past a simulated five-reader admissions committee for one college and round. It spells out the actors (first/second/essay/faculty readers and a dean) and the outputs (vote plus top 3 fixes), which makes it unmistakable against siblings like game_debrief or game_vote.

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 a clear prerequisite: the student must have shared their application text, otherwise ask them to paste it first. It does not name alternatives or when-not-to-use conditions (e.g., when to call compare or my_odds instead), so it stops short of full routing guidance.

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