Skip to main content
Glama

online_games

Read-only

Given the address of a page, returns what the page shows: the details of one game or its 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": "online_games"
  }
}

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 contributes one real behavioral fact — the response shape varies between a single game's detail and a list of games — which matters since there is no output schema. It says nothing about invalid or off-site URLs, empty results, or pagination.

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 well-formed sentence with the input precondition front-loaded and no filler. It is efficient, though 'returns what the page shows' is slightly vague and could be tightened to name the resource type directly.

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 tool with an annotated safety profile, the definition is minimally viable. However, it omits error behavior for malformed or non-site addresses and gives no basis for choosing between this tool and its two siblings, which is the main gap an agent would hit in practice.

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 description coverage is 100% and the single url parameter is already fully documented, including the 'full address or path starting with a slash' convention. The description's phrase 'the address of a page' adds no syntax or constraint beyond the schema, so 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?

The description names both the input (a page address) and the possible outputs (one game's details or a list of games), which is clearer than the name alone. But the verb is vague ('returns what the page shows') and it never distinguishes this tool from sibling games_results or top_games, leaving the agent unsure whether this is a generic page-fetch or a games-specific retrieval.

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 guidance at all: no indication of when this tool is preferred over games_results or top_games, no prerequisites, and no exclusions. The only usage signal is the implicit 'given a page address', which the schema already conveys.

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