Skip to main content
Glama

Scatter Slots UK

online_pokies

Read-only

An overview of all themed game collections published here, with a page address for each. 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": "online_pokies"
  }
}

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 adds that each collection comes with a page address, which is useful return-shape context, but it does not say how many items to expect, whether results are paginated, or what a 'page address' format is. It also does not explain the trailing 'Game collections: 1' fragment.

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 description is brief and front-loads the overview purpose, which is good. But the trailing fragment 'Game collections: 1' is cryptic — it is unclear whether it is a count of results, a category label, or a truncation artifact — and it dilutes an otherwise clean single sentence.

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 zero-parameter, read-only, no-output-schema tool, the description covers the essentials: it lists collections and mentions a page address per item. It still leaves the agent unsure about the shape of the response (fields per collection, item count, whether 'page address' is a URL) and about what 'Game collections: 1' means.

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 and the schema is a closed empty object, so there is nothing for the description to clarify. Baseline 4 applies; no parameter meaning is missing.

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 conveys that this returns an overview of themed game collections with a page address for each, which is a recognizable verb+resource. However, it never connects to the tool name 'online_pokies' or states that these are slot/pokie game collections, and it offers no differentiation from the sibling tools. An agent must infer the domain from the name alone.

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 guidance on when to call this versus alternatives, and no mention of siblings such as find_machines or machines. The only implicit cue is that it is a listing/overview call, which an agent could guess from almost any read tool.

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