Skip to main content
Glama

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": "pokies"
  }
}

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

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 earns some credit for disclosing the two possible return shapes (single-game facts vs. a game list), which matters because there is no output schema, but it says nothing about error behavior for bad addresses, whether pages are fetched live, or rate limits.

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 sentence, front-loaded with the verb and scope, with no wasted clauses. It could be tightened slightly ("what one page of the website shows" is a wordy way to say "fetches a page"), but the structure is sound.

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 fetch with annotations and no output schema, the definition covers the essentials and even hints at return shape. It remains thin on what "facts" concretely includes and what happens on an invalid or unreachable address, which is the main remaining gap.

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?

Schema coverage is 100% and the single url parameter is fully documented in the schema, so the schema carries the load. The description only loosely restates that the address identifies a page on this website; it adds no format detail, examples, or constraints 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 uses a concrete verb ("fetches") plus a concrete resource ("what one page of the website shows for a given address") and further specifies the two possible payloads: a single game's facts or a page's list of games. This is clear enough for an agent to act on, though it never explains the opaque name "pokies" and draws no explicit boundary against lookup_slots or online_slots.

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 when-to-use or when-not-to-use guidance and no named alternative. The only usage signal is implicit in "for a given address," which leaves the agent to infer when page-fetching beats the sibling slot-lookup tools.

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