Skip to main content
Glama

One product's price card

product
Read-onlyIdempotent

Where one product is cheapest today. action: find (from text, model, EAN or URL), get (by slug), variants (sizes, colours), history (daily lowest price), abroad (cheaper in another country).

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": {
      "action": "<action>"
    },
    "name": "product"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHistory days, max 365
sortNoproduct (default) or total (counts shipping)
limitNoMax rows
queryNoText, model, EAN or product URL (find)
actionYesOperation to run; help {topic:"product"} lists each one's arguments
detailNocompact (default) or full
localeNoLanguage, e.g. cs
offsetNoRows to skip
countryNoCountry code, e.g. CZ
productNoProduct slug (get, variants, history)
currencyNoCurrency code, e.g. CZK

Output Schema

NameRequiredDescriptionDefault
moreNoHow to fetch the next page
limitNo
totalNoAll matches, not just this page
offsetNo
returnedNo
cross_border_noteNo
commission_disclosureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"Operation to run; help {topic:\"product\"} lists each one's arguments"
    • changedInput schema / properties / currency / description
      Previous value: -"Currency code"New value: +"Currency code, e.g. CZK"
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "compact (default) or full",
      +  "enum": [
      +    "compact",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip",
      +  "type": "number"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "commission_disclosure": {
      +      "type": "string"
      +    },
      +    "cross_border_note": {
      +      "type": "string"
      +    },
      +    "limit": {
      +      "type": "number"
      +    },
      +    "more": {
      +      "description": "How to fetch the next page",
      +      "type": "string"
      +    },
      +    "offset": {
      +      "type": "number"
      +    },
      +    "returned": {
      +      "type": "number"
      +    },
      +    "total": {
      +      "description": "All matches, not just this page",
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is fully covered. The description adds modest behavioral context ('cheapest today' freshness scope, 'daily lowest price' granularity, cross-country comparison) but says nothing about rate limits, missing-data behavior, or pagination when using limit/offset.

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 sentences, front-loaded with the core value proposition before the action enumeration; every phrase carries information. The action list is dense but readable, and there is no filler or repetition.

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 an 11-parameter, 5-action tool with an output schema available, the description covers the main branching decision (action) and the two most important inputs (query, product). Remaining gaps – how sort/country/currency interact with specific actions, and paging semantics – are covered by the schema, so completeness is adequate but not exhaustive.

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 the schema already documents every parameter, including that 'query' is for find and 'product' is the slug for get/variants/history. The description largely restates that mapping rather than extending it, and adds no meaning for days, sort, country, currency, limit, or offset beyond the schema text. Baseline 3 applies.

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 concrete verb+resource: 'where one product is cheapest today', and the action list ('find', 'get', 'variants', 'history', 'abroad') scopes exactly what the tool returns. It does not explicitly differentiate itself from siblings such as 'search' or 'price_watch', so an agent must still infer the boundary between a single-product price card and a search/watch tool.

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?

Guidance is given at the action level, which is the primary selection decision: 'find' for text/model/EAN/URL, 'get' by slug, 'variants' for sizes/colours, 'history' for daily lows, 'abroad' for cross-country price gaps. What is missing is inter-tool guidance – nothing says when to prefer this over 'search' or 'price_watch', and no exclusions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources