wzrods Product Database
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 1.4/5 across 1 of 1 tools scored.
With only a single tool, there is no possibility of confusing it with another tool. The tool's purpose is unambiguous in the sense that it is the only available operation.
The tool name 'search' is a simple, clear verb, but with only one tool there is no broader pattern to evaluate. The name is not chaotic or inconsistent, so it earns a moderate score.
A single tool for a product database is too few for the apparent scope. The server likely requires additional operations such as retrieving or managing products, not just search.
Only a search tool is provided, with no support for basic database operations like get, create, update, or delete. This is a severely incomplete surface for a product database server.
searchDInspectwzrods ai mcp
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The input query. | |
| ai_search_options | No | Options for customizing the AI search behavior. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No behavioral traits are disclosed beyond annotations, and there are no annotations to fall back on. The description does not mention query semantics, limits, side effects, return structure, or any operational behavior. The full burden falls on the description, and it provides nothing.
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 extremely short ('wzrods ai mcp'), which might be concise in length, but it is under-specified and provides zero valuable content. It is not 'appropriately sized' for the tool's complexity; it is a placeholder.
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?
The tool has a complex nested input schema and no output schema, yet the description provides no context about functionality, return format, or error behavior. This is completely inadequate for an agent to understand when or how to invoke the tool.
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% (both 'query' and 'ai_search_options' have descriptions), so the baseline is 3. The description itself adds no parameter meaning, but the schema carries the weight. No extra semantics are provided, so it does not exceed baseline.
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 'wzrods ai mcp' is a brand/project name, not a description of functionality. It fails to state any verb, resource, or purpose, offering no clue that this tool performs searches. This is effectively missing and misleading.
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?
No usage guidance is provided. There is no mention of when to use this tool versus alternatives, no prerequisites, and no context about expected invocation. The description is entirely silent on usage.
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!
