Skip to main content
Glama

top_machines

Read-only

Retrieval of a page's content by its address: either the facts of one game 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": "top_machines"
  }
}

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 safety and scope are covered by structured data. The description adds a useful hint about the shape of the returned content (single-game facts vs. a game list), which goes beyond the annotations. It does not mention error behavior for invalid paths, auth requirements, or rate limits, so the addition is modest.

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, and the retrieval action comes first. The trailing "either the facts of one game or a list of games" is slightly loose phrasing that could be tightened, but nothing is wasted.

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 tool with full schema coverage and annotations, little more is strictly required, and the description does gesture at the return shape. However, the mismatch with the name top_machines and the absence of any routing guidance leave a real ambiguity an agent cannot resolve from the definition alone.

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, including the full-address-or-slash-path format and 300-character limit. The description's "by its address" merely restates that, adding no format, validation, or example detail beyond the schema. Baseline 3 applies when the schema does the work.

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 a concrete action and resource ("retrieval of a page's content by its address"), so the operation is identifiable. But it does not match the tool name top_machines, which implies listing top machines rather than fetching an arbitrary page, and it never distinguishes this tool from best_games or reels_finder. The agent can tell what the call does mechanically but not how it relates to its name or siblings.

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 when-not-to-use guidance, and no mention of the sibling tools best_games or reels_finder. The clause "either the facts of one game or a list of games" hints at two outcomes but never says which URLs or conditions produce which, leaving selection entirely to inference.

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