Skip to main content
Glama

Admissions game: the fixes

game_debrief
Read-only

App-only stage of admissions_game, called by the in-chat view after the vote. The committee chair writes the debrief: the three changes that would most help this application, each pointing to the student's own words. Simulation only; it never writes or rewrites essays.

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>",
      "run": "<run>",
      "readers": "<readers>"
    },
    "name": "game_debrief"
  }
}

Input Schema

NameRequiredDescriptionDefault
runYesThe run state returned by admissions_game (seating, readers and ids). Pass it back unchanged.
majorNoIntended major, if the student gave one.
roundNoApplication round: "ED", "ED2", "EA", "REA" or "RD".
schoolYesThe college the application is for, as the student named it (e.g. "Tufts").
visitsNoAny campus visits or contact with the college the student mentioned.
readersYesEvery reader's notes from game_read, keyed by reader.
applicationYesThe student's own application text (essays, activities, grades) exactly as they supplied it. Used for this run only; never stored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / application / description
      Added value: +"The student's own application text (essays, activities, grades) exactly as they supplied it. Used for this run only; never stored."
    • addedInput schema / properties / major / description
      Added value: +"Intended major, if the student gave one."
    • addedInput schema / properties / readers / description
      Added value: +"Every reader's notes from game_read, keyed by reader."
    • addedInput schema / properties / round / description
      Added value: +"Application round: \"ED\", \"ED2\", \"EA\", \"REA\" or \"RD\"."
    • addedInput schema / properties / run / description
      Added value: +"The run state returned by admissions_game (seating, readers and ids). Pass it back unchanged."
    • addedInput schema / properties / school / description
      Added value: +"The college the application is for, as the student named it (e.g. \"Tufts\")."
    • addedInput schema / properties / visits / description
      Added value: +"Any campus visits or contact with the college the student mentioned."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The readOnly and non-destructive annotations already cover the safety profile, and the description reinforces that profile rather than contradicting it: 'Simulation only; it never writes or rewrites essays.' That spells out the boundary of a simulation tool, where an agent might otherwise fear side effects on the student's material. What's missing is any note on cost, latency, or what happens to the run state it consumes.

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 short sentences that are front-loaded with what the tool is and what it produces. Nothing is repeated and no sentence is wasted.

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 usefully says what the response contains (three changes, each pointing to the student's own words). For a tool with nested parameters and simulation semantics, that is nearly complete, though a word on how the run state flows back would close the last gap.

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 every one of the 7 parameters, including the nested run and readers objects, is already documented in the schema. The description adds no syntax or format guidance beyond that. A 3 (baseline) is the right score.

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 (the debrief with the three changes that would most help the application) and its place in the pipeline (the app-only stage of admissions_game after the vote). The result it produces and its anchoring to the student's own words are concrete enough to separate it from game_read, game_vote, and game_done.

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 says when it runs: after the vote, driven by the in-chat view, not by the agent directly. That sequencing is clear, but it never names game_done, game_vote, or any alternative, and never states an explicit 'do not call before the vote' exclusion.

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