Skip to main content
Glama

How to play

how_to_play
Read-only

Rules, enemies, power-ups and how the step tool works. Read this first.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

readOnlyHint=true already tells the agent this is safe and side-effect free; the description adds the substantive detail that the content includes game rules plus how the 'step' tool behaves, which is not derivable from annotations or an empty schema. It does not state the output form (plain text vs structured) or that the content is static, so it is good but not complete.

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?

Two short sentences with no filler; every clause (rules, enemies, power-ups, step mechanics, read-first order) carries distinct information. The call-order instruction is slightly back-loaded but still unambiguous.

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 zero-parameter, read-only documentation tool with no output schema, a description needs to say what knowledge it delivers and when to call it — both are present. A statement of the return form would close the remaining gap.

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 to disambiguate and the baseline is 4. The description appropriately spends no words on parameters and instead covers content scope.

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 enumerates concrete content — rules, enemies, power-ups, and the semantics of the 'step' tool — so the agent knows this is the game's instruction/reference resource, and specifically one that explains a named sibling. It stops short of saying the tool returns explanatory text rather than performing any game action, which keeps it from a 5.

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?

'Read this first' gives explicit sequencing guidance: consult this before invoking step or the other game tools. There is no statement of when it is not needed (e.g., after the first read) and no named alternative, so it is clear context without 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