Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

xbox_game

Fetch Xbox catalog details for one product ID, including title, description, publisher, platforms, price, media, trailers, and Game Pass subscription availability.

Instructions

Get Xbox catalog details for a single product. Returns Xbox catalog details for a single product id: title, description, publisher, categories, supported platforms, content rating, price, preorder status, media (box art, poster, hero art), trailers, and which subscriptions (e.g. Game Pass) include it.

Input Schema

NameRequiredDescriptionDefault
localeNoDisplay locale (BCP-47)
product_idYesXbox catalog product id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It is clearly a read-only catalog fetch ('Get', 'Returns') and it enumerates the returned data fields, which is useful. However, it says nothing about auth/permission needs, rate limits, caching, or behavior on an invalid or unknown product id.

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 sentences, front-loaded with the core action before the field enumeration. The second sentence is a long comma-delimited list but every item is a concrete return field, so it earns its length. Slightly dense but no filler.

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 no output schema, the description steps up by enumerating the return contents (title, description, publisher, categories, platforms, rating, price, preorder status, media, trailers, subscriptions), which is exactly what an agent needs to judge relevance. The remaining gap is guidance on obtaining a valid product_id.

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%, with both locale (BCP-47) and product_id ('Xbox catalog product id') documented in the schema. The description repeats the product_id concept but adds no format, examples, or locale-behavior detail beyond the schema, so the 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?

States a specific verb and resource: 'Get Xbox catalog details for a single product,' then names the key input (a single product id). It distinguishes a single-item detail lookup from list/browse siblings implicitly, but never names xbox_search or xbox_browse, so sibling differentiation is left to inference.

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?

The phrase 'for a single product id' implies this is the per-item detail tool versus search/browse alternatives, but there is no explicit when-to-use instruction, no note that the id comes from xbox_search, and no exclusions. Usage is only implied.

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

Deploy Server

Other Tools