Neptune Cigars

Search Products In Stock

search_products

Read-only

Search buyable products (SKUs) on neptunecigar.com by name.

Returns live sellable items — exact vitola/packaging (single, 5-pack, box) — with current price, stock availability, and a direct product URL. Use search_cigars first to pick a line, then this to find what's in stock.

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": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`in_stock_only`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations only provide readOnlyHint, so the description adds meaningful behavioral context: it returns live sellable items with exact packaging, current price, stock availability, and a direct URL, and it is meant for name-based stock lookups after line selection. It does not disclose pagination or query matching details, but output schema and readOnly hint reduce the burden.

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?

Three tight sentences, each earning its place: purpose, return detail, and usage guidance. No redundancy or filler.

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?

The description is complete enough for an agent to invoke correctly: output schema covers return values, readOnlyHint covers safety, and the name-query + search_cigars-first workflow covers selection. Minor omissions are limit semantics and more precise query matching behavior, but these are not blocking.

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?

With 0% schema description coverage, the description must compensate. It explains query as searching by name and in_stock_only through 'find what's in stock,' but it never mentions the limit parameter's behavior, leaving a gap.

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 uses a specific verb and resource: 'Search buyable products (SKUs) on neptunecigar.com by name.' It also clarifies the output (live sellable items, exact vitola/packaging, price, stock, URL) and explicitly differentiates from search_cigars by prescribing it as the prerequisite step.

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

Usage Guidelines5/5

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

It gives a clear workflow: 'Use search_cigars first to pick a line, then this to find what's in stock.' This tells an agent when to use this tool versus the main alternative, and the 'by name' qualifier further narrows selection.

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

All Neptune Cigars tools Inspect

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

Need Help?