Skip to main content
Glama

Product catalog

adgpt_catalog

Product feeds and items: import a feed (xml|shopify), poll import status, and read and update products. Actions: list, get, createFeed, updateProduct, importStatus. Call adgpt_capabilities with the operationId to see an action's parameters.

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": {
      "action": "<action>"
    },
    "name": "adgpt_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoParameters for the action (see adgpt_capabilities).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the enumeration of createFeed/updateProduct is consistent with a mutating tool. The description adds one genuinely useful behavioral fact – that feed import is asynchronous and must be polled via importStatus – but says nothing about what an import overwrites, whether re-import is safe, or what happens on partial failure.

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?

Two sentences: the first states scope, the second enumerates the actions and the discovery mechanism. Front-loaded, no filler, and the action list doubles as a map to the enum.

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

Completeness4/5

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

For a five-action dispatcher with an opaque params object, the description covers the action menu and the two-step discovery path, and no output schema means return values need not be explained. The remaining gap is per-action guidance, which is delegated by design rather than forgotten.

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?

The schema documents the action enum fully but the params object is an untyped free-form bag at roughly 50% coverage. The description correctly delegates detail to adgpt_capabilities rather than silently omitting it, which is better than nothing but still gives no per-action parameter hints for the five operations.

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 names the resource (product feeds and items) and enumerates all five actions (list, get, createFeed, updateProduct, importStatus), so an agent knows the tool covers catalog feed ingestion and product reads/writes. It stops short of contrasting with siblings such as adgpt_upload_product_image, which sits adjacent to the 'update product' surface.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is actionable routing guidance in 'Call adgpt_capabilities with the operationId to see an action's parameters', which tells the agent how to proceed. However it never says when to pick this tool over siblings like adgpt_upload_product_image or adgpt_brands, and gives no exclusion conditions.

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