Skip to main content
Glama
Sign In

Sputnik X — AI-Agent-Native Intelligence

by xyz.sputnikx
OverviewDiscussionsAdmin

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

NameRequiredDescriptionDefault
slugYesTenant slug of a live tenant (e.g. thespot)
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.

  1. Changed2 schema fields changed
    • changedInput schema / properties / slug / description
      Previous value: -"Tenant slug"New value: +"Tenant slug of a live tenant (e.g. thespot)"
    • removedInput schema / properties / slug / enum
      Removed value: -[
-  "siltums",
-  "woodpoint"
-]
  2. 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"
+]
  3. 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, the description carries the full burden. It usefully discloses a data-safety trait not in the schema (returns safe columns, omits cost_price/markup), but omits other behavioral facts: that it is a non-mutating read, pagination/empty-result behavior, and any auth requirements beyond the tenant slug.

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 purpose, and zero filler. The return-value caveat is placed usefully but slightly compresses two distinct concerns (output scope and filtering) into one sentence.

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?

For a 6-parameter filtered list tool with full schema descriptions and no output schema, the description gives enough: purpose, filterable dimensions, and a return-scope caveat. A sentence on default result size or behavior on no matches would close the remaining gap.

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%, so parameters are already well documented and the baseline is 3. The description adds little beyond the schema, and slight imprecision: "category" is not a filter parameter, only a field matched by the free-text `search` input.

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 verb and resource ("Search products in a tenant catalog") and adds a scope qualifier (safe columns only). Sibling tools are unrelated domains, so no sibling ambiguity exists to resolve; naming them isn't necessary here.

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?

"Filter by type, category, name, or in_stock status" implies how the tool is used, but there is no explicit when-to-use/when-not guidance, no mention of prerequisites (tenant must be live is only in the schema), and no alternatives offered.

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

All Sputnik X — AI-Agent-Native Intelligence 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