Correkt: The AI-Native Online Marketplace for Physical Products
Server Details
Correkt: online marketplace built for AI agents. Shop 10M+ physical products from verified sellers.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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.
Tool Definition Quality
Average 4.6/5 across 1 of 1 tools scored.
With only one tool available, there is no possibility of ambiguity or overlap between tools. The agent has no alternative tools to confuse with search_products.
The single tool follows a clear verb_noun pattern (search_products). With only one tool, there are no conflicting conventions or styles to create inconsistency.
A marketplace server requires tools for cart management, checkout, and product details, but this server provides only search functionality. Having exactly one tool is far too few for the stated domain of an online marketplace.
The server is severely incomplete for a marketplace, offering only search while lacking essential operations like add_to_cart, view_product_details, or checkout. The tool description even references cart functionality that doesn't exist in the tool set.
Available Tools
1 toolsearch_productsAInspect
Search Correkt's catalog of over 10 million products.
Use this tool to find products by name, description, or category. Always use this before adding anything to cart.
Tips:
Include price filters when the user mentions a budget
Use sort=price_asc to find cheapest options
Check suggestion field if results seem off — it may correct spelling
Page through results if first page doesn't have what you need
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | page number | |
| sort | No | sort order | best_match |
| query | Yes | search query e.g. 'running shoes' | |
| max_price | No | maximum price filter | |
| min_price | No | minimum price filter | |
| page_size | No | results per page | |
| brand_name | No | filter by brand name | |
| category_id | No | filter by category UUID |
Output Schema
| Name | Required | Description |
|---|---|---|
| page | Yes | |
| products | Yes | |
| page_size | Yes | |
| suggestion | No | |
| total_hits | Yes | |
| max_price_available | Yes | |
| min_price_available | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Discloses spelling correction behavior ('suggestion field'), pagination support, and catalog scale. Missing potential rate limits or auth requirements, but covers primary behavioral traits (search logic, result handling).
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?
Well-structured with clear hierarchy: purpose → mandatory usage rule → tactical tips. Every sentence provides distinct value. No redundancy with schema definitions. Efficient use of space.
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?
Comprehensive for 8-parameter search tool with output schema. Covers search capabilities, result interpretation (spelling suggestions), pagination strategy, and workflow integration. Output schema exists, so omitting return value details is appropriate.
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 has 100% coverage (baseline 3). Description adds valuable usage context: price filters tied to budget mentions, specific sort recommendation (price_asc), and spelling correction awareness. Elevates raw schema definitions into actionable guidance.
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?
Opens with specific verb ('Search') and clear resource scope ('Correkt's catalog of over 10 million products'). Establishes search fields (name, description, category) immediately, providing complete functional context.
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?
Explicitly states prerequisite workflow: 'Always use this before adding anything to cart.' Clear when-to-use guidance that establishes tool sequencing. No siblings exist to compare against, but the cart dependency provides clear usage boundaries.
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.
Discussions
No comments yet. Be the first to start the discussion!