Skip to main content
Glama

free_machines

Read-only

Fetches what one page of the website shows for a given address: the facts of a single game or the page's list of games.

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": {
      "url": "<url>"
    },
    "name": "free_machines"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesLocation of a page on this website, given as a full address or a path starting with a slash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 useful context by disclosing that the response varies between single-game facts and a list of games, but it says nothing about paging behavior despite framing the result as 'one page', nor about what happens on a bad or off-site address.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One compact sentence with the action front-loaded and no filler. The phrasing around 'what one page of the website shows' is slightly indirect but the sentence is well within bounds for a simple fetch tool.

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 tool with full schema coverage, the main remaining burden is explaining return values since there is no output schema. The description partially does this by naming the two result shapes, but omits pagination guidance and error/fallback behavior, and leaves the name-to-behavior relationship unexplained.

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 at 100% schema coverage, the schema already documents the url field including the full-address-or-slash-path format. The description's 'for a given address' adds no format, constraint, or interpretation beyond what the schema states.

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 does give a verb (fetches) and a resource (one page of the website at a given address), and it names the two possible shapes of result: facts of a single game or a list of games. However, it never reconciles this generic page-fetch behavior with the tool name 'free_machines', so an agent cannot confidently predict what it is retrieving, and nothing distinguishes it from siblings like best_games or lookup_pokies.

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 statement of when to call this tool rather than best_games or lookup_pokies, and no prerequisites or exclusions. The only implicit guidance is that a URL is required, which the schema already says.

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