Skip to main content
Glama

Browse a platform

browse_platform
Read-onlyIdempotent

One platform's games with their prices, most popular first or by price: the most valuable games on a console, the cheapest, A to Z. Optionally only PAL, NTSC or Japanese releases.

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": {
      "platform": "<platform>"
    },
    "name": "browse_platform"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of games; a sort shows the platform's first 180.
sortNomost-listed (most popular, the default), name (A to Z), price (highest first), price-asc (lowest first).
limitNoGames a page, 1 to 60 (20 when left out).
regionNopal, ntsc-u (North America) or ntsc-j (Japan and Asia); every region when left out.
currencyNoCurrency for prices, an ISO 4217 code: USD (the default), EUR, GBP, CAD, AUD, JPY, PLN and others.
platformYesA platform slug from list_platforms, e.g. "super-nintendo".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / page / description
      Previous value: -"Page of games."New value: +"Page of games; a sort shows the platform's first 180."
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Games a page, 1 to 60 (20 when left out).",
      +  "maximum": 60,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / page / description
      Previous value: -"Page of games, 60 a page."New value: +"Page of games."
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety needs no restating. The description does add real context — a sort caps visible results at the platform's first 180, and omitted region/currency default to all regions and the server default. It omits pagination totals and whether prices can be absent.

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?

Two sentences, front-loaded with the resource and its sort options, then the optional region narrowing. Dense but readable; the phrase 'the most valuable games on a console' is slightly redundant with the sort list rather than a hard filler.

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 six-parameter list tool with full schema coverage and annotations, most calling information is present. The 180-item truncation note is valuable, but missing are pagination behavior near that cap and whether prices are omitted for unpriced games — the main remaining risks for correct invocation.

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%, with enums and defaults fully documented in the schema, so the baseline applies. The description only restates the sort directions and region choices in prose, adding no syntax or edge-case meaning beyond what the schema already gives.

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?

Names a specific verb and resource — a single platform's games with their prices — and enumerates sort orders and the region filter. It stops short of differentiating from siblings like search_games or get_game_prices, so scope against them is inferred only from the required platform parameter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The requirement for a platform slug plus the pointer that slugs come from list_platforms gives implied usage. There is no explicit statement of when to choose this over search_games or get_game_prices, so an agent must infer the browse-the-catalog framing.

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