Skip to main content
Glama

audit_catalog_quality

Read-only

Run catalog quality audit

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "audit_catalog_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
top_nNoNumero massimo di righe da restituire (intero).
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
wait_timeout_secNoSecondi massimi di attesa del risultato (intero).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / top_n / description
      Added value: +"Numero massimo di righe da restituire (intero)."
    • addedInput schema / properties / wait_timeout_sec / description
      Added value: +"Secondi massimi di attesa del risultato (intero)."
  2. First observed

TDQS

C2.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is known. The description adds nothing beyond that: it doesn't explain what the audit inspects, how long it takes (relevant given wait_timeout_sec), or what kind of result comes back.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with zero padding, which is structurally clean. But it is so thin that brevity here reads as under-specification rather than economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with three optional parameters, no output schema, and several look-alike audit siblings, four words are not enough: the agent cannot tell what gets audited, what top_n limits, or what the result represents. An output schema is absent, so the description should at least describe the shape of the outcome.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all three parameters (top_n, account_id, wait_timeout_sec) are already documented in the schema, including the note linking account_id to list_clients. The description contributes no additional parameter meaning; baseline 3 applies because the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Run catalog quality audit" does name a verb and a resource, so the purpose is not a pure tautology of the name. However, it gives no detail about what a "catalog quality" audit covers and does nothing to separate it from siblings such as audit_title_compliance, audit_aplus_coverage or audit_compliance, all of which the agent must already distinguish on its own.

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?

There is no when-to-use guidance at all: no prerequisites, no statement of when this audit is preferable to the other audit_* tools, and no exclusions. The agent must guess from the name alone.

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.

Resources