Skip to main content
Glama

FoxAPIs data sources

Steam game

steam_game
Read-onlyIdempotent

A Steam store page: price and discount, release date, genres, Metacritic score, achievements, developer and publisher, from its link. Costs 2 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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

Input Schema

NameRequiredDescriptionDefault
urlYesFor example: "https://store.steampowered.com/app/620/Portal_2/"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, and the description goes beyond them with two operationally important facts: it costs 2 credits per call, and an empty answer is not charged. It also flags the FoxAPIs key requirement, which is real pre-call context. It stops short of describing failure modes (invalid app ID, delisted pages) or response shape.

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 dense sentence that front-loads the resource and then lists returned fields, followed by cost and auth clauses. Every clause carries information; the field list is long but each item is a distinct return value, so it earns its space.

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 single-parameter read-only lookup with no output schema, the description supplies the return-field inventory, the credit cost rule, and the API-key prerequisite — enough to decide and invoke correctly. Missing only edge-case behavior for bad or non-Steam URLs, which is minor at this complexity.

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 parameter already carries a worked example URL, so the schema does the heavy lifting. The description's phrase 'from its link' confirms the parameter is a storefront link but adds no format rules, accepted URL variants, or app-ID handling. Baseline 3 applies when the schema fully documents the only parameter.

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 names the resource ('a Steam store page') and enumerates exactly what is returned — price and discount, release date, genres, Metacritic score, achievements, developer and publisher — plus the input basis ('from its link'). That is far more specific than a tautology, but it never distinguishes itself from platform siblings such as googleplay_app or appstore_app, leaving the platform separation implicit.

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?

Usage is implied rather than stated: the agent infers it should supply a Steam store URL and in return gets aggregated store metadata. There is no explicit when-to-use/when-not, no mention of what to do with a non-Steam URL, and no named alternatives despite several platform-analogue siblings.

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