Skip to main content
Glama

new_games

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

Input Schema

NameRequiredDescriptionDefault
urlYesPage address of this website, either complete or beginning with a slash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description doesn't need to restate safety. What it does add is meaningful: the result shape is polymorphic (single game facts vs. a page list), which matters a lot since there is no output schema. It omits error behavior for bad addresses and whether data is live or cached, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with no filler, and the key behavioral fact (two possible return shapes) is packed into the same sentence rather than buried later. Nothing here needs trimming or reordering.

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

Completeness4/5

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

For a one-parameter read tool with full schema coverage and annotations, the description covers the essentials and notably compensates for the absent output schema by describing the two possible result shapes. The remaining gap is guidance on choosing it over sibling page tools and on failure behavior for malformed addresses.

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 one parameter and 100% schema description coverage, the schema already explains that the address may be complete or start with a slash. The description contributes only the implication that the address determines whether a game detail or a list is returned, a modest semantic addition. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Fetches what one page of the website shows for a given address') and clarifies the two possible outcomes: a single game's facts or a page's list of games. It is clear enough to act on, though the name 'new_games' points toward a list-only tool and the description never names the website, leaving a small ambiguity an agent must resolve from context.

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?

The description gives no when-to-use or when-not-to-use guidance and never references alternatives such as lookup_machines or top_slots. An agent must infer from the names alone whether this page fetch is the right choice versus the other tools, which is exactly the decision the description should make.

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