Skip to main content
Glama
Sign In
MaxGaming MCP Server

MaxGaming MCP Server

by washedguy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_storefronts

Retrieve the supported countries, languages, currencies, and regions for MaxGaming to choose the correct storefront before searching or browsing products.

Instructions

List supported countries, languages, currencies and regions for MaxGaming.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_storefronts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
storefrontsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. "List supported ..." implies a harmless, static reference lookup, but it does not state that it is read-only, whether results are static or market-dependent, or whether any permissions are required. For a zero-parameter lookup tool the risk is low, hence a middle score rather than a penalty.

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?

A single sentence with no filler, and the key noun phrase (what is listed) is front-loaded immediately after the verb. Nothing is wasted or buried.

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 parameters and a published output schema, the description does not need to explain return values or argument formats. It covers the tool's scope adequately; the only minor gap is not stating whether these values are static or vary by market/session.

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?

The tool takes zero parameters, so per the baseline there is no parameter meaning for the description to add. The description does not need to compensate for any schema gap here.

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 gives a specific verb ("List") and a concrete resource (supported countries, languages, currencies, regions) scoped to MaxGaming. That is clearly distinct from the siblings browse_page, get_product and search_products, which all deal with product/page content rather than storefront reference data, though the description never explicitly draws that contrast.

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 only implied: an agent can infer this returns valid filter values (e.g. for country/language/currency arguments elsewhere), but the description never says when to call it, whether it must be called before other tools, or what alternatives exist. No when-not-to-use guidance is present.

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