Skip to main content
Glama
Sign In

BayDeep — The e-commerce plugin for AI agents

by io.github.MeshTok
OverviewDiscussionsAdmin

mint_free_key

SELF-SERVE a free API key — NO signup, NEVER expires, unlocks ALL tools (live AliExpress search, hot products, attributed convert links, your orders). Call this FIRST if any other tool says a key is required. Store the returned key and send it as X-API-Key header (or Authorization: Bearer) on subsequent calls. Rate limit: 30 req/min. Attribution is bound to this key. Optional client_ref ([A-Za-z0-9-], <=40) = your own end-user id, echoed back on your orders.

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

Input Schema

NameRequiredDescriptionDefault
client_refNooptional: your stable anonymized end-user id ([A-Za-z0-9-], <=40)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the rate limit (30 req/min), that keys never expire, that attribution binds to the key, and how to transmit it (X-API-Key or Bearer). The main gap is idempotency — it doesn't say whether calling twice returns the same key or mints a new one, which matters for a credential-creation 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 key facts are front-loaded in the opening clause, and the paragraph is dense with actionable information rather than filler. The parenthetical list of tool categories is slightly expendable, and the all-caps emphasis is stylistically loud, but overall it is tight.

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?

There is no output schema, so the description must convey the return contract; it does so partially by telling the agent to 'store the returned key' and noting client_ref is echoed back. It does not name the response field(s) or confirm what else is returned, a minor gap for a simple one-parameter credential tool.

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?

Schema coverage is already 100%, so the parameter is technically documented. The description adds real business meaning beyond the schema: client_ref is 'your own end-user id' that is 'echoed back on your orders', explaining why an agent would supply it rather than just its format constraints.

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 states a specific verb and resource — minting a free API key — and makes its role as a prerequisite explicit ('unlocks ALL tools', 'call this FIRST'), which clearly separates it from the sibling search/catalog tools. The purpose is unmistakable without opening the 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?

It gives a clear trigger condition: 'Call this FIRST if any other tool says a key is required', plus the context that the key unlocks all tools. There are no exclusions or when-not-to-use cases, but for a bootstrap credential tool, no plausible alternative exists, so the guidance is actionable.

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