Skip to main content
Glama
Sign In
CatalogReady

CatalogReady

by PO-VINCENT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

catalogready_audit_page_html

Audit product-page HTML to evaluate AI shopping agent readiness and get actionable fixes for improvement.

Instructions

Audit supplied product-page HTML; the host remains responsible for fetching it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>",
      "html": "<html>"
    },
    "name": "catalogready_audit_page_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
htmlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden. It only states the tool audits HTML and that the host fetches it, but does not disclose what the auditing entails, output format, or any side effects.

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

Conciseness4/5

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

The description is extremely concise with one sentence, front-loading the core purpose. However, it sacrifices detail, earning a 4 rather than 5.

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 no output schema and no annotations, the description is inadequate. It does not explain what the audit checks, what the return value is, or how to handle the url parameter, leaving the agent underinformed.

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?

Schema description coverage is 0%, and the description adds no meaning beyond the parameter names. It does not explain what 'url' and 'html' represent or how they relate to the auditing process.

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?

The description clearly states the tool audits supplied product-page HTML, with a specific verb ('audit') and resource ('product-page HTML'). It also distinguishes from fetching by noting the host is responsible for fetching.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies the tool does not fetch HTML, but does not mention sibling tools or provide exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools