Crawlora MCP

datasets_steam_achievements_item

Read-only

Fetch one stored achievement by the exact Steam app_id and achievement name returned by datasets_steam_achievements_search. The composite key identifies one app and its achievement; absent records return 404. Use datasets_steam_achievements_search to find achievement names.

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": {
      "app_id": "<app_id>",
      "name": "<name>"
    },
    "name": "datasets_steam_achievements_item"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Required achievement API name returned by datasets_steam_achievements_search.
`app_id`	Yes	Required Steam app id returned by datasets_steam_achievements_search.

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.

AddedNov 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description does not need to argue safety. It adds genuinely new behavior: lookup is keyed on the composite (app_id, name) pair and nonexistent keys yield 404 rather than an empty result. It does not discuss rate limits or data freshness, which keeps it short of a 5.

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?

Three compact sentences, front-loaded with the action and key requirement. The final sentence partially repeats the first sentence's pointer to the search tool, a small redundancy that keeps it from being perfectly tight.

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?

With only two fully documented parameters and an output schema in place, the description covers everything an agent needs: what it returns, what key it requires, where those key values come from, and how misses are signaled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameter descriptions already say 'returned by datasets_steam_achievements_search'. The description reinforces that these must be exact stored values from that search rather than free-form names, which is a useful semantic constraint beyond the schema text.

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: 'Fetch one stored achievement by the exact Steam app_id and achievement name'. It is clearly a singular lookup, which distinguishes it from the sibling datasets_steam_achievements_search that returns multiple records.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this tool once you already have the composite key, and use datasets_steam_achievements_search to discover achievement names first. It also states the absent-record behavior (404), so the agent knows what a miss means.

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?