Skip to main content
Glama

List products and prices

list_products
Read-onlyIdempotent

List every product and service sold on IP Computers with its id, vendor, category, monthly price in ILS before VAT, billing unit (per endpoint, user, server or month) and page URL. Items with quote_only=true are priced by quote. Shows an interactive catalog where the host supports MCP Apps.

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": "list_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoOptional category filter: endpoint, backup, cloud, monitor, manage or services.

Output Schema

NameRequiredDescriptionDefault
itemsYes
currencyYes
vat_rateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful context beyond annotations, especially that quote_only items are priced by quote and that an interactive catalog is shown only where the host supports MCP Apps.

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?

The description is front-loaded and dense with relevant information, with no filler. Each sentence contributes either output-field context, pricing nuance, or host-dependent behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, has a complete input schema, rich annotations, and an output schema, so the description does not need to explain return structure. It still covers the important quote_only nuance and the optional interactive catalog behavior, making the definition complete for correct invocation.

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?

There is only one optional category parameter, and the schema already documents it at 100% coverage with an enum. The description does not add syntax or filtering semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 uses a specific verb and resource: it lists every product and service sold on IP Computers. It also enumerates the returned fields, so an agent can tell this is a catalog-listing tool rather than a quote-building or single-product lookup tool.

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?

The description implies this is for browsing the full product catalog, and the optional category filter suggests narrowing by category. However, it does not explicitly say when to use this instead of siblings such as get_product or build_quote, so the routing guidance is only implied.

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