Skip to main content
Glama

Show pictures

show_pictures
Read-onlyIdempotent

Show original product pictures in chat. One ID shows all its pictures; several IDs show one per product in order.

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": {
      "product_ids": "<product_ids>"
    },
    "name": "show_pictures"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoDelivery country (ISO 3166-1 alpha-2). Default: client location, else DE.
product_idsYesIDs from results. One shows all pictures; several show one per product in order.

Output Schema

NameRequiredDescriptionDefault
picturesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, idempotent), so the burden is lower, and the description still adds real context: pictures are 'original' rather than thumbnails, they render inline in chat, and multiple IDs yield one picture per product in input order. It does not mention the 10-ID cap, but that is documented in the schema.

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 short sentences, zero filler, with the primary purpose front-loaded and the multiplicity rule following immediately. Nothing needs trimming.

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, full schema coverage, and an output schema handling return values, the description only needs to establish purpose and the batch behavior, which it does. The missing piece is comparative guidance against the two sibling tools.

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%, including an explicit description of the country default, so the baseline is 3. The description's cardinality sentence largely restates the product_ids schema description verbatim and says nothing about the country parameter, so it adds little meaning beyond the structured fields.

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 names a specific verb and resource ('Show original product pictures') and adds the rendering context ('in chat'), so an agent can tell this is a visual-retrieval tool rather than a data lookup like get_product_details. It stops short of naming how it differs from its siblings explicitly.

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: an agent can infer the tool is for viewing pictures, and the one-ID-vs-several-IDs rule hints at when to batch. There is no explicit statement of when to prefer this over get_product_details or search_products, and no prerequisites or exclusions are given.

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