Skip to main content
Glama

Medium Volatility Slots UK

machines_results

Read-only

Searches the names of game pages, game studio pages and collection pages for the entered text. Topics, themes and descriptions are not searched. Number of game reviews: 10

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": {
      "query": "<query>"
    },
    "name": "machines_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA game, studio or collection title, or a fragment of one, containing two or more characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 known and the description's job is lighter. The description usefully adds that matching is name-only across three page types, a real behavioral trait not in the schema. But the trailing 'Number of game reviews: 10' is unexplained — it is unclear whether it is a result cap, a page-size limit, or unrelated metadata — and nothing is said about ordering or result structure.

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 search scope and exclusion are front-loaded and efficient. The final sentence 'Number of game reviews: 10' is both cryptic and disconnected from the rest, so it does not earn its place as written.

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 single-parameter, read-only search with a fully described schema and no output schema, the core is covered: what is searched, what is not searched. The definition is still short on how many results return, whether matching is exact or partial, and what the dangling review-count line means, leaving real ambiguity for an agent planning a query.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With one parameter and 100% schema coverage, the schema already fully documents 'query' including min/max length and that fragments are allowed. The description only restates that the text is matched against page names, adding marginal semantics beyond the schema. Baseline 3 is appropriate.

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 gives a specific verb and resource set: it searches the names of game pages, studio pages and collection pages. It also sharply bounds scope by stating topics, themes and descriptions are not searched, which lets an agent tell what it will and won't match. It falls short of 5 because it never contrasts with the siblings best_machines or free_jackpots, and the tool name 'machines_results' does not obviously map to 'game page search'.

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?

Implicit usage guidance comes from the explicit exclusion of topic/theme/description searching, which tells the agent when this tool will fail to find something. However, there is no statement of when to prefer it over the sibling tools, nor any prerequisite or result-count guidance beyond the cryptic review line.

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