Skip to main content
Glama

PowerBankPortatil Store

Product details

get_product_details
Read-only

Get one product's name, price, stock, colour, capacity, image and URL by slug (any language), SKU or product id.

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

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language (default en)
slugYesProduct slug from search_products, e.g. magnetic-powerbank-10000mah-white

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "en",
      -  "es",
      -  "fr",
      -  "de"
      -]New value: +[
      +  "en",
      +  "fr",
      +  "es",
      +  "de",
      +  "it",
      +  "pt",
      +  "nl"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With readOnlyHint and openWorldHint already supplied, the description adds useful behavioral context by listing the returned fields and noting language flexibility. The claim that lookup can be done by SKU or product id is potentially misleading because the schema only exposes a 'slug' parameter.

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 compact sentence that front-loads the action, resource, and returned fields. There is no filler or redundant wording.

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 read-only detail tool with no output schema, the description gives enough context about what will be returned and how lookup works. The only gap is the unresolved mismatch between the advertised SKU/product-id lookup and the schema's single slug parameter.

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 both parameters. The description adds some meaning, such as slug being usable in any language and mentioning SKU/product id lookup, but the latter is ambiguous or inconsistent with the schema's single 'slug' parameter.

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 states a specific verb and resource ('Get one product') and enumerates the returned attributes (name, price, stock, colour, capacity, image, URL), making the tool's purpose immediately clear and distinguishable from search_products.

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: fetch a single product when you already have an identifier. However, the description does not explicitly say to use this after search_products or when not to use it instead of other tools.

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