Skip to main content
Glama

Get a hint

game_hint
Read-only

One hint for the player's current position on a board: the single next step, never the whole answer. Each hint counts on the player's score.

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": "<game>",
      "number": "<number>"
    },
    "name": "game_hint"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYesWhich game, by id from list_games (for example "thunk").
numberYesBoard number (No. 1 was the game's first day).
progressNoEverything the player has done on this board from the start, in the game's own format (list_games describes each). Empty for nothing yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior1/5

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

The description says each hint counts on the player's score, which implies a state-changing penalty or score mutation. This contradicts the readOnlyHint=true annotation, which asserts the tool does not modify its environment. Although it usefully discloses the partial-answer nature of the return, the score-counting claim directly conflicts with the annotation.

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 description is two short sentences, front-loading the hint scope and then the scoring consequence. There is no filler or redundant restatement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 3-parameter tool with full schema coverage, the description adequately covers the return granularity and mentions the scoring consequence. However, it omits explicit usage routing to siblings and leaves the score-counting side effect unreconciled with the read-only annotation, which is a meaningful completeness 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 the schema already documents game, number, and progress. The description adds no additional parameter semantics beyond that structured coverage, making the baseline 3 appropriate.

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?

The description states a specific resource and scope: one hint for the player's current board position, specifically the single next step rather than the whole answer. That clearly separates it from a full-answer or result-style tool, though it does not explicitly name sibling alternatives such as game_move.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives no explicit guidance on when to use this hint tool versus alternatives like game_move or game_result. The note that hints count on the score is a relevant cost signal, but it is not framed as when-to-use or when-not-to-use 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