Skip to main content
Glama

List the puzzle games

list_games
Read-only

The Absurdly Obvious daily puzzle games: id, name, rules, scoring and the progress format each game uses with the other tools.

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": "list_games"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without description help. The description adds one piece of genuine context beyond that — that each game carries a "progress format" used by the other tools, hinting this is the reference/discovery call. It says nothing about result size, ordering, or whether the list is static.

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

Conciseness3/5

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

One sentence with no padding, which is appropriately sized for a zero-arg tool. But it is not front-loaded with an action verb, and the trailing clause "the progress format each game uses with the other tools" is grammatically tangled and easy to misparse. It is short rather than well-structured.

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?

With no parameters and no output schema, the description usefully stands in for the missing return contract by naming the fields each game record contains (id, name, rules, scoring, progress format). Combined with annotations covering safety, an agent has enough to call it correctly. Minor gap: it does not say how many games are returned or whether results are ordered.

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?

The tool takes zero parameters, so there is nothing for the schema to document and the baseline of 4 applies. The description does not need to compensate for any coverage gap and correctly spends no words on arguments.

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

Purpose3/5

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

The description names the resource ("The Absurdly Obvious daily puzzle games") and enumerates the fields it surfaces (id, name, rules, scoring, progress format), which implies enumeration. However, it contains no verb of its own — the agent must borrow "List" from the title — and never states that it returns ALL games at once. The purpose is inferable but not stated outright.

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?

There is no when-to-use guidance at all: nothing tells the agent to call this before game_move or game_hint, nor any precondition or exclusion. The trailing phrase "with the other tools" gestures at interoperability with siblings but does not explain what to do with it. The agent must infer routing purely from tool names.

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