Skip to main content
Glama

free_pokies

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_pokies"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage address of this website, either complete or beginning with a slash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 the useful behavioral detail that the response shape varies by page type (single-game facts vs. a game list), but it says nothing about pagination behavior, empty results, or fetch failures, despite "one page" implying a paginated source.

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?

A single front-loaded sentence with no filler, and the two possible content types are listed compactly after the colon. The phrasing "what one page of the website shows" is slightly roundabout but still efficient.

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 no output schema, the description is minimally adequate: it sketches what comes back (facts or a list). It is missing how the variable response is structured and whether a page yields more results than are returned, which matters since no output schema documents the return value.

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?

The single `url` parameter has 100% schema coverage, including the allowance for a full address or a leading-slash path, so the schema already carries the semantics. The description only restates "a given address" and adds no format or constraint detail beyond the schema.

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 names a specific verb ("Fetches") and resource ("what one page of the website shows for a given address"), and it clarifies that the returned content can be either a single game's facts or a list of games. That is a clear purpose, but it offers no differentiation from the sibling `search` tool, which likely also returns games.

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 explicit when-to-use or when-not-to-use guidance. The agent must infer that this tool applies when it already has a page address, rather than narrowing down from a query — the obvious alternative (`search`) is never mentioned.

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