Skip to main content
Glama
Sign In

BayDeep — The e-commerce plugin for AI agents

by io.github.MeshTok
OverviewDiscussionsAdmin

product_detail

Full detail for up to 10 AliExpress product ids (comma separated or array). Read-only. Requires a free API key.

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": {
      "product_ids": "<product_ids>"
    },
    "name": "product_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idsYescomma separated ids, max 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the behavioral burden and does provide two useful facts: 'Read-only' (safety profile) and 'Requires a free API key' (auth prerequisite). It says nothing about rate limits, error behavior for invalid/expired ids, or output shape, so the disclosure is partial rather than rich.

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?

Two short sentences, front-loaded with the core capability and followed by the two operational facts an agent needs. Nearly zero waste, though the redundant 'max 10 / up to 10' repetition and the questionable 'or array' clause keep it from being flawless.

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?

A single-parameter read tool with a fully documented schema and no output schema; the description covers what it returns (full detail), the batch limit, read-only nature, and the API-key requirement. That is sufficient to call it correctly, with only return-format expectations left unspecified.

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 coverage is 100% and the schema already documents 'comma separated ids, max 10', so the baseline is 3. The description's only addition is 'or array', which actually conflicts with the schema's string type and could mislead formatting; the max-10 repetition adds nothing new.

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?

States a specific resource (AliExpress product ids) and what is returned ('full detail'), plus the batch ceiling of 10, so an agent knows this is an id-based detail lookup rather than a discovery/search call. It does not name a sibling such as search_products to route agents that lack ids, so it stops short of full differentiation.

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?

Usage is only implied: 'for up to 10 product ids' signals that the caller must already hold ids, which contrasts with a search tool, but the description never says 'use after search_products' or states exclusions. An agent can infer the precondition but gets no explicit when/when-not guidance.

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