Skip to main content
Glama

Admissions game: the meeting and vote

game_vote
Read-only

App-only stage of admissions_game, called by the in-chat view after every reader has finished. The fictional committee discusses the readers' notes and votes Accept, Waitlist or Deny under the school's round, and returns the conversation and the vote. Simulation only.

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

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false and idempotentHint=false. The description adds meaningful context beyond that: the committee is fictional, the tool is simulation-only, it consumes readers' notes, and it returns both the conversation and the vote. It does not cover permissions or output detail beyond the return summary, but the safety profile is already carried by annotations.

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 sentences, front-loaded with the stage and invocation context, followed by the specific action and return, then the simulation caveat. Every sentence earns its place with no repetition or filler.

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?

For a nested-object, seven-parameter tool with no output schema, the description covers the essential invocation context, the decision behavior, the returned value, and the simulation-only boundary. The only minor gap is that it does not repeat that the run object must be passed back unchanged, but the schema explicitly documents that.

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 all seven parameters are already documented in the input schema. The description reinforces that readers' notes and the school's round drive the vote, but adds no syntax or format details beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb and resource: the fictional committee discusses readers' notes and votes Accept, Waitlist or Deny, returning the conversation and vote. It also distinguishes itself from the broader admissions_game and game_read stages by identifying itself as the app-only stage called after every reader has finished.

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 invocation context: it is the app-only stage of admissions_game, called by the in-chat view after every reader has finished. It does not explicitly name alternatives or exclusions, but the sequencing constraint and 'App-only stage' phrase substantially narrow when it should be used.

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