Skip to main content
Glama

Submit score

submit_score

After the game is over, enter your final score into the shared top 100 leaderboard under 1 to 3 letters. Returns your rank. Once per game.

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": {
      "game_id": "<game_id>",
      "initials": "<initials>"
    },
    "name": "submit_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
game_idYesThe game_id returned by new_game.
initialsYes1 to 3 letters A to Z.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does reasonably well: it discloses the write target (shared top 100 leaderboard), the once-per-game constraint, the timing prerequisite, and that a rank is returned. Failure modes — invalid game_id, calling twice, score overflow beyond top 100 — are not described.

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, front-loaded with the precondition and side effect, with zero filler. Each sentence contributes a distinct fact: timing, destination, return value, and frequency limit.

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 two-parameter game tool with no output schema, the description covers the prerequisite, the side effect, the duplicate-call constraint, and what is returned. Error behavior is the only meaningful omission.

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 100% and both parameters are self-documented, so baseline would be 3; the description goes slightly further by tying game_id to new_game and restating the initials constraint in prose. It adds little genuinely new semantics, so it lands just above baseline rather than higher.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — enter a final score into the shared top 100 leaderboard — plus the returned value (rank). It is clearly distinguishable from siblings like get_state and new_game, though it never names high_scores as the read-side counterpart.

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 timing precondition ("after the game is over") and a frequency limit ("once per game"), which is exactly the guidance needed to invoke it correctly. It stops short of naming an alternative tool or stating what happens if called before game end or a second time.

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