UCP agentic-commerce proxy for Estroni: merino & low-tox women's activewear catalogue.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 3.8/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion between tools. The tool has a clear, singular purpose of searching policies and FAQs.
The single tool name follows a clear verb_noun convention, making it consistent and predictable. No mixed styles or irregular patterns exist.
A single tool for a storefront is far too few to cover the expected functionality such as product browsing, cart management, order placement, or account features. This is an extreme mismatch between tool count and the server's apparent scope.
The tool surface is severely incomplete, covering only policy and FAQ lookups. Essential storefront operations like product search, order tracking, and customer support are entirely missing, leaving agents with dead ends for most tasks.
search_shop_policies_and_faqsAInspectUsed to get facts about the stores policies, products, or services. Some examples of questions you can ask are:
What is your return policy?
What is your shipping policy?
What is your phone number?
What are your hours of operation?"
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | A natural language query. | |
| context | No | Additional information about the request such as user demographics, mood, location, or other relevant details that could help in tailoring the response appropriately. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must carry the burden of behavioral disclosure. It states the tool is used to 'get facts,' implying a read-only search, but offers no detail on output format, limitations, or behavior when no answer is found. Basic but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and well-structured: a single opening sentence followed by a short bulleted list of examples. Every element earns its place, with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple FAQ search tool with only two flat parameters and no output schema, the description provides adequate usage examples and scope. It doesn't describe return type, but the tool's behavior is straightforward enough for an agent to infer.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for both parameters ('query' and 'context'). The description does not add parameter-level detail beyond what the schema already states, so it provides no additional semantic value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('get facts') and names the resource ('stores policies, products, or services'), making the general purpose clear. However, including 'products' creates ambiguity with sibling tools like get_product_details and search_catalog, so it doesn't fully distinguish from siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Clear context is provided via concrete examples of acceptable questions (return policy, shipping policy, phone number, hours). It doesn't explicitly state when not to use the tool or mention alternatives, but the examples imply this is for policy and FAQ queries.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Sign in to create a connector for this server.