Skip to main content
Glama

Markan: Steam market data

Estimate lifetime sales and revenue

estimate_sales
Read-only

Rough lifetime sales and net revenue (low/medium/high) for up to 50 Steam games, computed exactly like Markan's spreadsheet add-ins: reviews x a release-year multiplier (Boxleiter method), and list price x sales x a factor for refunds, regional pricing, discounts, tax and Steam's cut. Estimates, not reported figures.

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": {
      "steam_ids": "<steam_ids>"
    },
    "name": "estimate_sales"
  }
}

Input Schema

NameRequiredDescriptionDefault
steam_idsYesSteam app IDs (the number in a store URL), from find_games or search_games.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / steam_ids / description
      Added value: +"Steam app IDs (the number in a store URL), from find_games or search_games."
  2. First observed

TDQS

A4/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 adds real value by disclosing the estimation methodology (Boxleiter review multiplier, price x sales with refund/regional/discount/tax/cut factors) and, critically, that results are estimates rather than reported figures. The only gap is no mention of latency or computation cost for 50 games.

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?

Front-loaded with the deliverable and its granularity, then one clause of methodology, then the caveat. Every sentence carries information an agent needs; nothing is redundant.

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 tool with no output schema, the description covers output shape (low/medium/high, sales and net revenue) and accuracy expectations well. Only minor omissions remain, such as result ordering or behavior when an ID is invalid.

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 a single parameter at 100% schema coverage, the schema already documents that these are Steam app IDs drawn from find_games or search_games. The description's 'up to 50 Steam games' merely restates the maxItems constraint, adding no new semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource up front — 'Rough lifetime sales and net revenue (low/medium/high) for up to 50 Steam games' — and the methodology sentence pins down exactly what is being computed. Nothing about this could be confused with the find_games/search_games siblings, which only resolve IDs.

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 context is implied rather than stated: the reader infers this is the tool to call once app IDs are known, and the 50-game cap sets a practical scope. The description never explicitly says when to choose it versus alternatives or what to do beyond the cap, leaving that to the schema note about find_games/search_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