audit
Audit a product for agent-readiness.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes |
StackResolve
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'Audit a product for agent-readiness,' which implies a read-only analysis but does not explicitly state side effects, permission requirements, or what the tool actually does (e.g., checks documentation, API quality, or something else). It provides minimal behavioral transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short, which is not necessarily conciseness but under-specification. It front-loads the core purpose, but it omits essential details about parameter usage, expected outcomes, and operational behavior. The brevity reduces its usefulness rather than enhancing it.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This tool has one required parameter, no output schema, no annotations, and a description that provides no additional context. The definition is far from complete: it does not clarify what the domain should be, what the audit will return, or what 'agent-readiness' means in practice. An agent using this tool without further information would likely fail to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema describes a single required parameter 'domain' as a string, but there is zero description coverage (0%). The description does not explain what 'domain' refers to (e.g., a website URL, product name, or unique ID). Since the schema provides no semantics and the description adds none, agents have no basis for correctly populating the parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: auditing a product for agent-readiness. It identifies a specific verb (audit) and resource (product), and it is distinct from sibling tools that focus on comparison, pricing, or company research. However, it does not elaborate on what 'audit' entails or what aspects of agent-readiness are evaluated, so it stops short of full clarity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no context on when to use this tool versus alternatives. It does not mention any prerequisites, typical scenarios, or exclusions. An agent has to infer that audit is intended for assessing a product's agent-readiness but receives no guidance on when it would be preferable to research_company, get_profile, or find_tools_for_task.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.6/5.0
Disambiguation2/5
resolve and find_tools_for_task both return ranked tool recommendations for a task, and how_to also surfaces recommendedTools, making their boundaries unclear. search_tools adds further overlap as a registry search by query and requirements. The company/research and registry lookup tools are more distinct, but the task-to-tool cluster is genuinely confusing.
Naming Consistency4/5
The naming is almost entirely snake_case verb_noun: get_company, find_competitors, search_tools, compare_products, list_registry. The exceptions are audit and resolve as bare verbs and how_to as an idiom, but they are still recognizable.
Tool Count4/5
Fifteen tools is at the upper end of a reasonable range, and the broad scope of registry lookup, research, comparison, audit, and interface generation supports a larger surface. However, find_tools_for_task largely duplicates resolve, so the count is slightly higher than necessary.
Completeness4/5
The server covers the main registry lifecycle: listing, searching, getting records, comparing, researching, pricing, readiness auditing, and generating agent interfaces. It is intentionally read/research-oriented, so the lack of registry CRUD is not a severe gap. Minor missing pieces like direct per-product OpenAPI retrieval or registry entry management are workable around.