Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

datasets_steam_achievements_item

Retrieve a single Steam achievement record by app ID and achievement API name to inspect global achievement details stored in the search dataset.

Instructions

Get one stored Steam achievement. Retrieves one global achievement record by appid and name from datasets_steam_achievements_search.

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	Achievement API name
`app_id`	Yes	Steam app id

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden, but 'stored'/'global' does at least signal a cached read-only lookup of a global achievement definition (not per-user unlock data). It does not disclose not-found behavior, error semantics, or what fields a record contains, which matter for an unannotated tool.

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?

Two short sentences, front-loaded with the action and resource, with zero filler. The second sentence partially repeats the first ('Get one stored...' / 'Retrieves one global...'), so it is efficient but not maximally tight.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter item lookup with fully covered schema and no output schema, the core need is met: the keys and the source collection are identified. However, with no annotations and no output schema, the description leaves return content and failure behavior unaddressed, so it is complete only at a minimum-viable level.

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%, so both parameters are already documented in the schema as 'Steam app id' and 'Achievement API name'. The description restates `appid`/`name` as the lookup keys without adding format, casing, or relationship details beyond the schema, so baseline 3 applies.

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 a specific verb ('Get'/'Retrieves') and resource ('one global achievement record'), and scopes it by the two required keys `appid` and `name`. It also points back to `datasets_steam_achievements_search`, which lets an agent infer the item-vs-search relationship, though the contrast is stated as provenance rather than as an explicit 'use search instead for listing' rule.

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: by saying records come 'from `datasets_steam_achievements_search`', it hints the agent should search first and then fetch this item by key. There is no explicit when-to-use/when-not-to-use guidance or note about what happens for a missing key.

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

Deploy Server