Skip to main content
Glama

games

Read-only

Supplies the content of one page from the page address, whether that is a game's details or a 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": "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

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 safety and locality are covered. The description usefully adds that the same call serves both detail and listing pages, but says nothing about what 'content' means (raw markup vs. parsed fields), pagination, or failure behavior on an invalid path.

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 compact sentence with the core action front-loaded and no filler. The phrasing 'from the page address' is slightly redundant with 'page' appearing twice, but nothing needs to be cut.

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?

There is no output schema, so the description carries the burden of indicating what comes back, and 'the content of one page' is vague about return shape and structure. Combined with thin usage guidance, this leaves meaningful gaps for a tool whose whole job is fetching varied page types.

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?

With a single parameter and 100% schema description coverage, the schema already documents that url is a full address or slash-prefixed path. The description adds only the mild clarification that the target page may be a game detail or a game list, which is useful but marginal beyond the schema baseline.

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 states a concrete verb-and-resource pair: it 'supplies the content of one page' identified by a page address, and clarifies the two page kinds it covers (a game's details or a list of games). An agent can tell this is a fetch-by-URL tool, though it does not distinguish itself from siblings like machines_search.

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, no exclusions, and no mention of alternatives. The phrase about game details vs. a list of games hints at scope but is descriptive, not directive about when to choose this tool over the sibling search 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