Skip to main content
Glama

KW Commercial Kitchen Equipment Finder

get_product

Read-onlyIdempotent

Read one exact product_id or canonical slug from search_products. Returns existing public specifications, warranty, current AUD prices including and excluding GST, website supply status and KW product link. Missing/discontinued/hidden identities return product_not_found.

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": {
      "identity": "<identity>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
identityYesExact numeric product_id or canonical product slug returned by search_products. Use search_products for a SKU/model; no fuzzy identity lookup.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds genuine behavioral value on top: it enumerates what is returned (specs, warranty, AUD prices incl/excl GST, supply status, KW link) and defines the failure behavior ('product_not_found' for missing/discontinued/hidden identities), which is information the annotations cannot convey.

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 sentences, zero filler, and the identity constraint plus the routing hint are front-loaded before the return/error details. Every clause carries distinct information.

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?

With no output schema, the description compensates by listing the returned fields and the not-found outcome. Combined with a single fully-documented required parameter, an agent has everything needed to invoke and interpret this call.

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%, and the schema itself already documents the exact-id vs. slug constraint and the no-fuzzy-lookup rule. The description's mention of 'one exact product_id or canonical slug' largely restates the parameter description, so the baseline 3 applies.

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?

States a specific verb and resource ('Read one exact product_id or canonical slug') and explicitly ties the identity source to the sibling tool search_products. An agent can distinguish it from search_products without reading either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative ('Use search_products for a SKU/model') and states an exclusion ('no fuzzy identity lookup'), which tells the agent exactly when this tool is the wrong choice. This is a full when/when-not/alternative statement.

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