Crawlora MCP

steam_achievements

Read-only

Fetch a Steam app's achievement records and global unlock percentages by numeric appid, sorted most-unlocked first. Apps without global achievement stats return an empty list. Use steam_app for app details, steam_reviews for reviews, or datasets_steam_achievements_search for stored history.

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": {
      "appid": "<appid>"
    },
    "name": "steam_achievements"
  }
}

Input Schema

Name	Required	Description	Default
`appid`	Yes	Numeric Steam app id

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026
- addedInput schema / properties / appid / description
```
Added value: +"Numeric Steam app id"
```
First observedOct 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds useful behavior: results are sorted most-unlocked first and apps without global achievement stats return an empty list. It does not discuss auth or rate limits, but the output schema covers return structure.

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?

Three sentences, front-loaded with purpose and ordering, then an edge-case behavior, then sibling routing. Every sentence earns its place and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 Steam lookup with an output schema and annotations, the description supplies purpose, ordering, empty-result behavior, and sibling routing. Nothing essential for correct invocation is missing.

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?

There is one required parameter and schema description coverage is 100%; the schema already documents it as 'Numeric Steam app id'. The description repeats 'numeric appid' but adds no format or syntax details beyond the schema, so the baseline is 3.

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 (fetch), resource (achievement records and global unlock percentages), key (numeric appid), and ordering (most-unlocked first). This is enough to distinguish it from sibling tools like steam_app and steam_reviews.

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

Usage Guidelines4/5

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

Explicitly names alternatives for other needs: steam_app for app details, steam_reviews for reviews, and datasets_steam_achievements_search for stored history. It does not spell out an explicit when-not-to-use condition beyond routing to siblings, so it falls just short of the highest level.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?