Skip to main content
Glama

Get product details

get_product
Read-only

Full details of one product by its slug: description, active ingredient, how to use, warnings, price and availability.

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

Input Schema

NameRequiredDescriptionDefault
slugYes
currencyNoAlso show prices in this currency (USD, EUR, GBP, RUB); approximate, at today's rate. Payment is in EGP. Default EGP only.
languageNoLanguage of the answer: en, ar, ru, it or de. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / currency
      Added value: +{
      +  "description": "Also show prices in this currency (USD, EUR, GBP, RUB); approximate, at today's rate. Payment is in EGP. Default EGP only.",
      +  "enum": [
      +    "USD",
      +    "EUR",
      +    "EGP",
      +    "RUB",
      +    "GBP"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds useful context that the payload includes price and availability, but says nothing about what happens on an unknown slug, whether prices are live or cached, or what currency the base price is in — that detail lives only in the schema's currency description.

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?

A single front-loaded sentence with no filler: it identifies the resource, the lookup key, and the returned fields in one pass. Nothing is wasted or repeated from the title.

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?

There is no output schema, so the enumeration of returned fields (description, active ingredient, how to use, warnings, price, availability) is genuinely necessary and present. For a three-parameter read tool with annotations covering safety, the only meaningful omission is failure behavior for an invalid slug.

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 67%, with the currency parameter already documented in detail (approximate conversion, payment in EGP) and language enumerated. The description only restates the slug key and the fact that price appears in the output, adding no syntax, format, or fallback guidance beyond the schema, so 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 specific verb and resource ('Full details of one product') plus the lookup key ('by its slug'), and enumerates the returned fields, so an agent can immediately tell it apart from list/search-style siblings. It stops short of naming search_products or browse_category as the alternative paths, so it is clear but not fully differentiated.

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 only implied: the tool requires a slug, which signals 'use when you already have an exact product identifier' and contrasts with discovery tools. There is no explicit when-to-use, when-not-to-use, or statement about what to do if only a product name is known, leaving the agent to infer the routing.

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