Skip to main content
Glama

Get product details

get_product
Read-onlyIdempotent

Get one product or service by id: description, highlights, price, billing unit, page and Markdown URLs, and the direct purchase URL when it is sold online.

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_id": "<product_id>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesProduct id from list_products, for example "s1-complete" or "rmm".

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
nameYes
unitNo
vendorNo
buy_urlNo
highlightsNo
quote_onlyNo
descriptionNo
markdown_urlNo
price_ils_before_vatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds one genuine behavioral nuance — the purchase URL is returned only "when it is sold online" — but says nothing about failure behavior for an unrecognized id or any access constraints.

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 front-loaded sentence that identifies the resource, the lookup key, and the returned fields with no filler. Every clause carries information.

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 an output schema present and a fully documented single enum parameter, the description need not explain return structure, and it correctly stops at summarizing contents plus the conditional purchase URL. Only the discovery path for product_id and error handling are absent, both minor here.

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 single parameter is a closed enum with an example, so the schema carries the load. "by id" restates what the schema already specifies without adding format, sourcing, or fallback guidance.

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 ("Get one product or service by id") and enumerates the payload (description, highlights, price, billing unit, URLs, purchase URL), which makes the read-one nature clear against a list-style sibling. It never names an alternative, so differentiation is inferred rather than stated.

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: fetch a single product by its id. There is no explicit when-to-use, no rule for handling ids not present, and no pointer to a listing tool for discovering ids (that hint lives in the schema, not the description).

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