Skip to main content
Glama
Sign In

Shop Nobi

by ai.nobi
OverviewDiscussionsAdmin

Check price and availability

check_price_and_availability
Read-onlyIdempotent

Returns the current price, currency, whether it is in stock, and the stock count when the store gives one, for one or more products found in a product search, taking their ids from the search results. Store catalogs are kept constantly refreshed, so the price and stock are up to date. There is no price history, as the catalogs keep none. For follow-up calls in this conversation, send the visitorId returned by a previous result unchanged. Omit it on the first call; do not invent one.

Input Schema

NameRequiredDescriptionDefault
idsYesNobi variant ids, each from a product search result.
visitorIdNoFor follow-up calls in this conversation, send the visitorId returned by a previous result unchanged. Omit it on the first call; do not invent one.

Output Schema

NameRequiredDescriptionDefault
productsYes
visitorIdNoFor follow-up calls in this conversation, send the visitorId returned by a previous result unchanged. Omit it on the first call; do not invent one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / visitorId
      Added value: +{
+  "description": "For follow-up calls in this conversation, send the visitorId returned by a previous result unchanged. Omit it on the first call; do not invent one.",
+  "format": "uuid",
+  "maxLength": 36,
+  "minLength": 1,
+  "type": "string"
+}
    • addedOutput schema / properties / visitorId
      Added value: +{
+  "description": "For follow-up calls in this conversation, send the visitorId returned by a previous result unchanged. Omit it on the first call; do not invent one.",
+  "format": "uuid",
+  "maxLength": 36,
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / ids / description
      Previous value: -"The ids of the products, each from a product search result."New value: +"Nobi variant ids, each from a product search result."
    • changedInput schema / properties / ids / items / description
      Previous value: -"The ids of the products, each from a product search result."New value: +"Nobi variant ids, each from a product search result."
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely non-schema context: catalogs are continuously refreshed so values are current, and no price history exists anywhere. Missing is any statement about behavior for unknown ids or partial results.

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?

Returns are front-loaded in the first sentence, followed by freshness, scope limits, and the visitorId protocol — a sensible ordering. It loses a point only for restating the visitorId guidance already present in the schema.

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?

With rich annotations, an output schema, and full schema coverage, the description needs to carry little, and it still explains the return shape and data-freshness caveats. The one remaining gap is that the batch limit of 20 and handling of invalid ids are left entirely to the schema.

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%, and the visitorId sentence in the description is a verbatim copy of the schema's field description, so no new meaning is added. The ids parameter gains only the framing that they originate from a prior search, which the schema already says.

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 names a specific operation and enumerates exactly what comes back: price, currency, stock flag, and conditional stock count, for one or more products. It also delimits scope by ruling out price history, so an agent can separate this from get_product_details or search_products without opening a 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 states the input source clearly — ids must come from a product search result — and gives an explicit rule for the visitorId across turns (omit first call, pass unchanged after, never invent). It stops short of naming when to prefer compare_products or find_alternatives, so no explicit alternatives are offered.

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

All Shop Nobi 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