Sputnik X — AI-Agent-Native Intelligence

get_prices

Get current product prices with calculated price_per_kg. Returns EUR pricing for all in-stock products.

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": {
      "slug": "<slug>"
    },
    "name": "get_prices"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	Tenant slug of a live tenant (e.g. thespot)
`product_slug`	No	Specific product slug (optional — omit for all)
`response_format`	No	Response detail level: "concise" (default, key fields only) or "detailed" (all fields)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

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"
-]

Changed3 schema fields changedSep 4, 2026

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"
+}

addedInput schema / properties / slug

Added value: +{
+  "description": "Tenant slug",
+  "enum": [
+    "siltums",
+    "woodpoint"
+  ],
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "slug"
+]
```

First observedMar 14, 2026

TDQS

A3.6/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 discloses useful behavioral context: returns EUR pricing, only for in-stock products, and includes calculated price_per_kg. However, it does not state that the operation is read-only, nor does it mention any rate limits, authentication requirements, or error behavior.

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 waste. The core purpose is front-loaded, followed by essential scoping details (currency, in-stock filter, calculated field).

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 simple price-retrieval tool with no output schema, the description is fairly complete: it states what is returned (EUR pricing), the filter (in-stock products), and an added value (calculated price_per_kg). Minor gaps like pagination or response structure are less critical here given the simple operation.

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 three parameters in detail. The description adds no parameter-specific semantics beyond what the schema provides; baseline 3 is appropriate.

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 ('Get') and resource ('current product prices'), and adds scope details like calculated price_per_kg and EUR pricing for in-stock products. It does not explicitly differentiate itself from the sibling tool search_products, leaving the agent to infer the distinction.

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 implied by the description ('Get current product prices'), but there is no explicit guidance on when to use this tool versus alternatives such as search_products, nor any mention of prerequisites or exclusions.

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 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.