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
urlYesFull page address or a slash-prefixed fragment of this site.

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?

The annotations already state readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds genuinely useful behavioral context about the response shape — it returns either a single game's facts or a page's game list — but says nothing about failure behavior for invalid addresses or whether the result is paginated.

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 front-loaded sentence communicates the operation, the input contract, and the two possible return shapes with no filler. It is tight, though the clause after the colon is slightly dense and could be split for readability.

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?

With one required parameter, no output schema, and annotations carrying the safety profile, the description covers the essentials. It stops short of clarifying what 'facts' actually comprise or how the single-game vs list outcome is distinguished, which is the remaining gap an agent would want filled.

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?

There is a single parameter with 100% schema description coverage (full page address or slash-prefixed fragment), so the schema already does the work. The description only echoes 'a given address' and adds no format, normalization, or example detail beyond the schema, which is the baseline case.

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 (fetches) and a clearly bounded resource: the rendered content of one page at a given address, which may be a single game's facts or a list of games. That is enough for an agent to know this is a page-read tool, but it never contrasts itself with the siblings jackpots or lookup_slots, so differentiation is left to inference.

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?

Usage is only implied: it says this returns page-level content for an address, which suggests it is the general retrieval tool, but there is no explicit when-to-use statement, no exclusions, and no mention of when to prefer lookup_slots or jackpots instead.

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