Skip to main content
Glama

Scatter Slots UK

find_machines

Read-only

Matches pages of games, game studios and collections by name only; the given text is not looked for in themes or descriptions. Number of game reviews: 17

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "s": "<s>"
    },
    "name": "find_machines"
  }
}

Input Schema

NameRequiredDescriptionDefault
sYesFull or partial name of a game, game studio or collection, at least two characters long.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 read-only closed-domain profile is covered. The description contributes the meaningful behavioral detail that matching is strictly name-based, but it also appends 'Number of game reviews: 17', an unrelated statistic that conveys nothing about this tool's behavior and risks confusing the agent.

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 first sentence is front-loaded and dense with useful constraints, but the trailing 'Number of game reviews: 17' is dead weight that does not belong in a tool definition. Removing it would make this an efficient two-clause description.

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 one-parameter read-only lookup this covers the essentials of what is searched and what is not, and the absence of an output schema means return values need not be explained. It is still ambiguous whether 'pages of' means paginated results or page-like entities, and offers no guidance on result counts or limits.

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?

With one parameter at 100% schema coverage the baseline is 3, and the description earns an increment by clarifying what the string is compared against (names only, not themes or descriptions), which the schema does not say. It still leaves matching looseness (substring vs fuzzy, case sensitivity) unstated.

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?

States a concrete matching operation over a clearly enumerated resource set: pages of games, game studios and collections. The 'by name only' qualifier sharpens what is being matched, but the description never distinguishes this tool from its siblings 'machines' or 'online_pokies', leaving the agent to infer that relationship.

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

Usage Guidelines3/5

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

The clause 'the given text is not looked for in themes or descriptions' is a useful exclusion that tells the agent when this tool will fail. However, no alternative tool or query route is named for the theme/description case, so the agent must discover the fallback itself.

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