Crawlora MCP

xbox_game

Read-only

Fetch Xbox catalog details for one game, including publisher, platforms, content rating, price, preorder status, and media. Use xbox_search to find games, xbox_browse for discovery, or xbox_collection for a collection.

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": {
      "ProductID": "<ProductID>",
      "Locale": "<Locale>"
    },
    "name": "xbox_game"
  }
}

Input Schema

Name	Required	Description	Default
`Locale`	Yes	Display locale (BCP-47), default en-US.
`ProductID`	Yes	Xbox catalog product id (12-character StoreId, shared with the Microsoft Store catalog).

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.

First observedOct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the returned field set, which is useful, but nothing about auth, rate limits, or locale-dependent behavior beyond what the annotations and output schema carry.

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?

Two sentences, front-loaded with the action and returned fields, followed by routing. Zero wasted prose.

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?

With an output schema present and full schema coverage, the description needn't explain returns. It covers purpose and routing adequately; only minor gaps (prerequisite of a resolved ProductID, locale default behavior) remain, both of which the schema documents.

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 description coverage is 100% and both parameters (ProductID, Locale) are documented in the schema, including the 12-character StoreId detail and BCP-47 locale. The description adds no parameter-level meaning, so baseline 3 applies.

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) and resource (Xbox catalog details for one game), then enumerates the payload (publisher, platforms, content rating, price, preorder status, media). An agent can distinguish it from xbox_search, xbox_browse, xbox_reviews, and xbox_collection without opening any schema.

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 routes the agent to three alternatives with their roles: xbox_search for finding games, xbox_browse for discovery, xbox_collection for collections. It doesn't state the precondition for using this tool itself (an already-known ProductID), but the routing context is clear.

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?