Skip to main content
Glama
kavingas

Catalog Services MCP Server

by kavingas

get_environment_store_views

Retrieve all store views and websites for an Adobe Commerce Cloud environment. Returns a list of store view codes grouped by website.

Instructions

Get all store views for a specific environment.

This is a convenience tool that retrieves environment details and extracts
all store view information in a flattened structure for easier use.

Args:
    environment_id: Adobe Commerce Cloud environment ID
    timeout: Request timeout in seconds (default: 15.0)
    
Returns:
    Dict containing:
    - status: Success or error status
    - environment_id: The queried environment ID
    - store_views: List of all store views with their codes
    - websites: List of all websites with their codes
    - count: Number of store views found
    
Example:
    >>> result = get_environment_store_views('7059bb71-341a-4ccb-b543-d7b2948b73e4')
    >>> for sv in result['store_views']:
    ...     print(f"{sv['websiteCode']}/{sv['storeCode']}/{sv['storeViewCode']}")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeoutNo
environment_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It describes the tool as retrieving environment details and extracting store views, and mentions the return structure. However, it does not disclose any behavioral traits like idempotency, side effects, or required permissions.

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?

The description is well-structured with Args, Returns, and Example sections. It is somewhat lengthy but each part is relevant. The example is helpful. Slight over-explanation could be trimmed, but overall effective.

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?

The tool has two parameters and no output schema in the data, but the description defines the return structure in detail. It provides enough context for an agent to understand inputs and outputs. However, it does not mention any prerequisites or typical usage patterns relative to sibling tools.

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?

Schema description coverage is 0%, so description must compensate. It provides clear semantics for both parameters: environment_id is an Adobe Commerce Cloud environment ID, and timeout is in seconds with a default of 15.0. This adds meaning beyond the minimal schema.

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 clearly states the tool gets all store views for a specific environment, using a specific verb and resource. It distinguishes itself from sibling tools like find_store_view_codes by focusing on a flattened structure of store views, websites, and codes.

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 description explains it is a 'convenience tool' that retrieves environment details and extracts store views, implying it is an alternative to get_environment_details. However, it does not explicitly state when to use this tool vs alternatives, nor does it provide exclusions or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kavingas/catalog-services-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server