A
license-
qualityC
maintenanceEnables AI agents to search, compare, buy, and sell products across multiple e-commerce platforms through 13 marketplace tools.
Last updated
1
MIT
Correkt: The AI-Native Online Marketplace for Physical Products
by com.correkt
Server Details
Correkt: online marketplace built for AI agents. Shop 10M+ physical products from verified sellers.
- Status
- Unhealthy
- 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.
MCP client
Glama
MCP server
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.
100% free. Your data is private.
Tool Definition Quality
A4.1/5.0
Tool DescriptionsA
Average 4.5/5 across 1 of 1 tools scored.
Server CoherenceB
Disambiguation5/5
With only a single tool, there is no possibility of confusion between tools. The tool's purpose is clear and distinct.
Naming Consistency5/5
A single tool name is trivially consistent with itself. No naming pattern issues exist.
Tool Count1/5
The server claims to be an online marketplace for physical products but provides only a search tool. This is an extreme mismatch between scope and tool count; a marketplace requires many more tools for cart, checkout, user management, etc.
Completeness1/5
The tool surface is severely incomplete for a marketplace. Only product search is available, lacking essential operations like adding to cart, placing orders, viewing user profiles, or managing listings.
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
ParametersJSON Schema
| 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
ParametersJSON 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
A4.5/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behavior. It mentions pagination, spelling correction (suggestion field), and hints at result quality checks, but does not explicitly state read-only nature, auth requirements, rate limits, or behavior on no results. Adequate but not comprehensive.
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?
Concise: one core sentence, one usage directive, and three bulleted tips. No unnecessary words. Front-loaded with purpose. Each sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations or siblings, and presence of output schema (context signal), the description covers search initiation, pagination, sorting, filtering, and result verification via suggestion field. Enough for an agent to use the tool correctly in most scenarios.
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?
All 8 parameters have schema descriptions (100% coverage). The description adds value beyond schema by contextualizing their use (e.g., price filters for budget, sort for cheapest, suggestion field for spelling). This helps the agent apply parameters effectively.
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?
Clearly states the tool searches a catalog of 10 million products by name, description, or category. The verb 'Search' and resource 'products catalog' are specific, and the description distinguishes this as a pre-cart search tool, though no siblings are listed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states 'Always use this before adding anything to cart.' Provides actionable tips: use price filters on budget mentions, use sort=price_asc for cheapest, check suggestion field for spelling corrections, and page through results. This fully guides when and how to use.
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!
Related MCP Servers
- AlicenseAqualityDmaintenanceKlarna-style product discovery for AI shopping agents. Makes product catalogs machine-readable so AI agents can search, compare, and purchase products programmatically.Last updated6MIT
- Alicense-qualityCmaintenanceEnables AI agents to discover, price, and purchase SaaS products, developer tools, and MCP servers with live Stripe checkout, affiliate program, and AgentTrust verification.Last updatedMIT
- AlicenseAqualityBmaintenanceCross-border product catalog for AI agents. Search and compare products from US and South East Asian markets via Model Context Protocol.Last updated6946MIT
