Skip to main content
Glama

top_slots

Read-only

The themed collections of games published on this website and the page address of every collection. Game collections: 1

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description contributes that results include page addresses for every collection, which is useful return-shape context, but it does not clarify ordering, pagination, or what 'Game collections: 1' means operationally.

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?

The size is fine, but the structure is awkward: it leads with a long noun phrase instead of an action, and the trailing fragment 'Game collections: 1' is unclear and reads like leftover data. Trimming or reframing as one clear sentence would improve it.

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?

With no output schema, no parameters, and simple read-only annotations, the description only needs to explain what comes back. It gestures at that (collections and their page addresses) but leaves the return shape and the meaning of the '1' unresolved, so it is adequate but not complete.

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 description to disambiguate and the baseline of 4 applies. No parameter-related misinformation is present.

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 text names the resource (themed game collections plus each collection's page address) but uses a noun phrase with no verb, so it describes content rather than stating an action like 'list' or 'return'. An agent can guess this is a listings tool, but the purpose is only implied, and the fragment 'Game collections: 1' adds ambiguity rather than a specific scope.

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?

No when-to-use guidance is given, and neither sibling (lookup_machines, new_games) is referenced. The agent gets no signal on when to prefer this tool over the alternatives, and no prerequisites or exclusions are stated.

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