Skip to main content
Glama

pokies

Read-only

Reports the subject of a single page, identified by address: a game's facts or the games the page lists.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description adds no behavior beyond that: it doesn't say what is returned, how a page that matches neither category is handled, or whether the address must resolve within this site. For a read tool with no output schema, that is a thin contribution.

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 or repetition. It is efficient, though the terseness borders on cryptic for a tool whose name is not self-describing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description is the only place the return value could be explained, and "reports the subject" leaves the response shape ambiguous — an agent cannot tell whether it gets a classification label, a game record, or a list. For a one-parameter lookup tool this is under-specified rather than merely brief.

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 url property already documents "Full page address or a slash-prefixed fragment of this site." The description's "identified by address" restates that without adding format, normalization, or error semantics, so the baseline 3 applies.

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?

"Reports the subject of a single page, identified by address" gives a verb and a resource, and the clause "a game's facts or the games the page lists" hints at two page types. But "reports the subject" is abstract rather than a concrete action (classify? fetch? summarize?), and nothing distinguishes it from siblings like find_reels or new_jackpots. The opaque name "pokies" pushes extra weight onto the description, which only partly carries it.

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 versus find_reels or new_jackpots, no mention of prerequisites, and no exclusion cases such as what happens with a URL outside this site. The reader must infer usage entirely from the noun phrase.

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