Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

balenciaga_stores

Fetch physical Balenciaga store data by country, including addresses, coordinates, phone numbers, opening hours, and service flags. Pass a two-letter country code to query the directory.

Instructions

List Balenciaga stores. Returns Balenciaga's public physical-store directory for one country, including addresses, coordinates, phone numbers, opening hours, and store-service flags. Use balenciaga-store-countries to discover the complete accepted country enum.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYesTwo-letter country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden and does well: it indicates the data is public, scoped to one country, and enumerates the output contents (addresses, coordinates, phone numbers, opening hours, service flags). It doesn't mention pagination or response envelope, but that's a minor gap for a read-only directory tool.

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 with no filler. The verb and resource are front-loaded, the return contents are summarized, and the helper tool reference is placed last.

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?

For a one-parameter read-only listing tool, the description covers purpose, scope, input, and expected return contents. It loses a point because the helper is written as 'balenciaga-store-countries' while the actual sibling tool is 'balenciaga_store_countries', and because the phrase 'complete accepted country enum' slightly conflicts with the enum already present in the schema.

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% and the only parameter, country, already has a type, enum, and description. The description adds little beyond pointing to the sibling for the country enum, which is mostly redundant since the schema already lists accepted codes. Baseline 3 is appropriate.

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?

The description opens with a specific verb and resource ('List Balenciaga stores'), states that it returns a public physical-store directory for one country, and lists the returned fields. This clearly distinguishes it from the sibling balenciaga_store_countries.

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?

It gives clear context: one country at a time, public store directory, and it points the agent to balenciaga-store-countries for the accepted country enum. It doesn't explicitly state when not to use the tool, but there are no close alternative tools for store listings.

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