Skip to main content
Glama

Storewire Lite demo store

Show chosen products

show_products
Read-onlyIdempotent

Chosen Trailhead Supply products named by public_id, drawn as cards, or as a recommendation: groups by placement with the product, swaps, accessories and a live total. Names, prices and stock are the store's.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "show_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupsNoA recommendation: one group per placement. Give either this or public_ids.
localeNoAnswer language: en (default en). Names, labels and URLs follow it.
cart_tokenNoAn open cart's cart_token. The answer returns it while that cart is live.
public_idsNopublic_id of each product to show as a card.

Output Schema

NameRequiredDescriptionDefault
urlNo
viewYes
titleNoThe heading of a recommendation.
totalNoHow many products the list shows.
groupsNoThe recommendation view.
productsNoThe list view: the products, in the order given.
truncatedNoPresent and true only when the answer outgrew the size budget and its last list items were left out; ask narrower to see them.
cart_tokenNoThe cart_token given, while that cart is live; otherwise null.
answer_typeNoWhat this answer is, for rendering.
total_labelNoThe sentence over a recommendation's total.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that results include a computed 'live total' and that names, prices and stock come from the store, which is useful beyond the annotations, but it says nothing about cart_token lifetime behavior or what happens when no valid public_ids are supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the resource, but the prose is stylized to the point of obscurity ('drawn as cards', 'are the store's'), which costs a beat of comprehension for no informational gain. A plainer sentence would carry the same content more efficiently.

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 a full output schema, complete parameter descriptions and annotations covering the safety profile, the remaining description burden is light. The definition covers both invocation modes and data freshness adequately; only routing guidance to sibling tools is absent.

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%, so the schema already documents groups, public_ids, locale and cart_token, justifying the baseline 3. The description only loosely maps its own vocabulary ('swaps', 'accessories') onto the schema's alternates/addons fields, adding marginal clarity but no format or constraint detail beyond the schema.

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 gives a concrete verb and resource ('show ... products') and constrains the scope to already-chosen products identified by public_id, rendered either as cards or as a placement-based recommendation. That implicitly separates it from search_products and compare_products, though neither sibling is named 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: 'Chosen ... products named by public_id' tells the agent it needs IDs in hand, and the 'cards, or as a recommendation' phrasing hints at the two input modes. There is no explicit when-to-use/when-not guidance and no pointer to search_products for obtaining public_ids first.

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.