Skip to main content
Glama
Sign In

BayDeep — The e-commerce plugin for AI agents

by io.github.MeshTok
OverviewDiscussionsAdmin

catalog_overview

WHAT BAYDEEP SELLS: product types currently in the catalog (physical goods from AliExpress, flight fares via Travelpayouts/Aviasales), item counts, top categories, and HOW to search/book each type. Call this FIRST when unsure what the catalog contains. Works WITHOUT any API key. Read-only.

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": "catalog_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does answer two key questions: "Works WITHOUT any API key" (no auth prerequisite) and "Read-only" (no mutation risk). It does not characterize the shape or size of the response beyond the content list, which is a minor residual gap for a zero-parameter discovery tool.

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 front-loaded with a capped WHAT header and packs contents, entry-point guidance, and auth/read-only facts into three short sentences. The parenthetical vendor examples are slightly dense but each clause adds real information, so there is little waste.

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?

With zero parameters and no output schema, the description has to convey what comes back, and it does so through the content enumeration (types, counts, top categories, search/book guidance). It stops short of describing the response's structure or granularity, which would help an agent decide whether it needs a follow-up call.

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

Parameters4/5

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

The tool takes no parameters, so the baseline is 4. The description correctly implies the tool is parameter-free by describing a fixed overview rather than a filtered query, and there are no parameter semantics that need explaining.

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 names the resource concretely and enumerates what it covers: product types in the catalog (AliExpress physical goods, Travelpayouts/Aviasales flight fares), item counts, top categories, and how to search or book each type. That is specific enough that an agent can distinguish it from sibling tools like categories or search_products without opening any schema.

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

Usage Guidelines4/5

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

There is explicit when-to-use guidance: "Call this FIRST when unsure what the catalog contains." That is a clear positioning statement for an entry-point tool. It does not say when NOT to use it or name a specific alternative for deeper category browsing, which keeps it short of a 5.

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

All BayDeep — The e-commerce plugin for AI agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources