Skip to main content
Glama

Markan: Steam market data

Search Steam games

search_games
Read-only

Find Steam games and DLC by title (or by Steam ID). Returns up to 5 matches, most-reviewed first.

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": {
      "query": "<query>"
    },
    "name": "search_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPart of the title, or a numeric Steam ID.

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?

Beyond the read-only and closed-world annotations, the description adds useful behavioral detail: it returns up to 5 matches ordered by most-reviewed first. It does not discuss pagination, no-match behavior, or authentication, but the annotations already cover the safety profile.

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?

The definition is two concise sentences with the core search purpose and result behavior front-loaded. Every sentence carries useful information without filler.

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 simple one-parameter search tool, the description provides enough to invoke it correctly: accepted query forms and result count/order. The main gap is the absence of sibling differentiation, but the core invocation details are present.

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 schema already describes the single query parameter as either part of a title or a numeric Steam ID. The description repeats that meaning without adding syntax, matching rules, or other details beyond the schema.

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 specific verb and resource: find Steam games and DLC by title or Steam ID. It is clear what the tool does, but it does not explicitly distinguish itself from similarly named siblings such as find_games or get_games.

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 explains what the tool searches but not when to use it instead of alternatives. There is no explicit when-to-use or when-not-to-use guidance relative to find_games or get_games.

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