Skip to main content
Glama

market

by xyz.sputnikx

search_products

Search products in a tenant catalog. Returns safe columns only (no cost_price/markup). Filter by type, category, name, or in_stock status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesTenant slug
typeNoProduct type filter (e.g., granulas, briketes, saplaksnis)
limitNoMax results (default: 50, max: 100)
searchNoSearch text (matches name, type, category)
in_stock_onlyNoOnly show in-stock products (default: true)
response_formatNoResponse detail level: "concise" (default, key fields only) or "detailed" (all fields)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changed
    • addedInput schema / properties / in_stock_only
      Added value: +{
+  "description": "Only show in-stock products (default: true)",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max results (default: 50, max: 100)",
+  "type": "number"
+}
    • addedInput schema / properties / response_format
      Added value: +{
+  "description": "Response detail level: \"concise\" (default, key fields only) or \"detailed\" (all fields)",
+  "enum": [
+    "detailed",
+    "concise"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / slug / description
      Previous value: -"Specific product slug for single-product lookup"New value: +"Tenant slug"
    • addedInput schema / properties / slug / enum
      Added value: +[
+  "siltums",
+  "woodpoint"
+]
    • addedInput schema / required
      Added value: +[
+  "slug"
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly warns that the tool returns only safe columns, excluding cost_price/markup, which is valuable behavioral context beyond what the schema offers. It does not mention other behaviors like response format or pagination, but the safe-column disclosure is a strong transparency signal.

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 with zero filler. The main purpose and the critical safe-column caveat are front-loaded, followed by a concise list of filter dimensions. Every word earns its place.

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?

Given the moderate complexity (6 params, no output schema) and 100% schema coverage, the description is largely complete. It covers what the tool does, what it returns (and excludes), and how to narrow results. The only minor gap is no explicit guidance on when not to use it, but the safe-column note and sibling context partially cover this.

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 description coverage is 100%, so the schema already documents all six parameters effectively. The description's mention of filters ('by type, category, name, or in_stock status') adds a compact summary but no new semantic detail beyond what each parameter description already states.

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 ('Search') and resource ('products in a tenant catalog'), making the tool's purpose immediately clear. It also distinguishes itself from siblings like get_prices by noting it returns safe columns only, which prevents confusing it with price-related tools.

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?

The description clearly states the context: searching products within a tenant catalog with filters by type, category, name, or in-stock status. It does not explicitly name alternatives or exclusions, but the context is sufficiently clear for an agent to decide when to use this tool.

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

All market toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources