Skip to main content
Glama

Admissions game: finished

game_done

App-only. Called by the in-chat view when an admissions_game run ends, to record that it finished (school, AI token use and duration only; no application text). Returns nothing the user sees.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "game_done"
  }
}

Input Schema

NameRequiredDescriptionDefault
usageNoAI token counts for the run.
schoolNoThe college the run was for.
secondsNoHow long the run took.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / school / description
      Added value: +"The college the run was for."
    • addedInput schema / properties / seconds / description
      Added value: +"How long the run took."
    • addedInput schema / properties / usage / description
      Added value: +"AI token counts for the run."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already indicate a non-read-only, non-destructive, non-idempotent write. The description adds useful behavioral context: only school, AI token use, and duration are recorded, no application text is captured, and nothing is returned to the user.

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?

The definition is two tight sentences with no wasted material. The app-only constraint, trigger condition, data scope, and return behavior are all front-loaded or clearly ordered.

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?

For a small, app-triggered recording tool with full schema coverage and annotations covering its mutation profile, the description is complete enough. It explains the trigger, recorded data, privacy boundary, and user-visible return behavior.

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 coverage is 100%, so the three parameters are already fully documented. The description reinforces the data scope by saying 'school, AI token use and duration only; no application text,' but it adds little syntax or format detail beyond the schema.

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?

The description states a specific action and resource: recording that an admissions_game run has finished. It also scopes the tool as app-only and tied to the in-chat view, which distinguishes it from sibling tools such as admissions_game and game_debrief.

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?

The description clearly states when the tool is called: when an admissions_game run ends, from the in-chat view. It implies the tool is not meant for direct agent use by saying 'App-only,' but it does not explicitly name alternatives or exclusions.

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