Skip to main content
Glama

DeducePuzzles

Grade an arrangement

submit_attempt

Use this when the user submits an order for today's DeducePuzzles board (seating, floor, box, scheduling, or order and ranking). Grades that one arrangement: right or wrong, attempts left, and whether the round is finished. A wrong guess does not say which clues it broke. The solution is included only once the round is finished. A percentile is included only when the arrangement is right, this is the player's first completed round today, the solve took at least five seconds, and at least five ranked solves of today's board exist here. A replay, a round that already saw the solution, or a solve under five seconds states no percentile. A placement exists only in this result. Do not use to grade a puzzle this server did not serve. Attempts are counted per conversation, not per person.

Input Schema

NameRequiredDescriptionDefault
attemptIdYesConversation id returned by get_daily_puzzle. Attempts are counted per conversation, not per person. Pass this same id on every later call in the conversation.
arrangementYesEvery person from today's board exactly once, in the order the question asks. Index 0 is position 1 (lowest floor, left end of a row, rank 1, or day 1). Example: ["Aman", "Beena", "Chetan", "Diya"].
playerTokenNoAnonymous token returned by an earlier get_daily_puzzle. Pass it back to keep this app's streak. Omit it to start a new one. Not an account, and not a website streak. 16–64 letters, digits, _ or -.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With annotations only marking it non-read-only and non-idempotent, the description carries the real behavior: wrong guesses reveal nothing about which clues broke, the solution appears only after the round finishes, percentile has four stated gating conditions and several suppression cases, and attempts are per-conversation. This is exactly the context an agent cannot get from the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the trigger, then the result semantics, with no filler sentences. The percentile clause is dense but every condition stated materially affects how the agent reports the result.

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?

No output schema exists, yet the description fully describes the return surface: correct/incorrect, attempts remaining, round-finished flag, solution exposure, percentile and placement presence. Nothing an agent needs to interpret or relay the result is missing.

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% and the description largely restates what the schema already says (attemptId is per-conversation, arrangement ordering is question-driven). It adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 object (grades one arrangement for today's DeducePuzzles board) and enumerates the supported board types, making it clearly distinct from get_daily_puzzle (serves the puzzle) and get_hint (gives a clue).

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

Usage Guidelines5/5

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

Gives an explicit trigger ('when the user submits an order for today's ... board') and an explicit exclusion ('Do not use to grade a puzzle this server did not serve'), plus the implicit prerequisite that the attemptId comes from get_daily_puzzle.

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