Skip to main content
Glama

get-product-by-id

Retrieve a single product's full details using its unique numeric ID, enabling quick product lookups and catalog data access.

Instructions

Fetch a single product details using its unique ID

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": {
      "id": "<id>"
    },
    "name": "get-product-by-id"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe numeric ID of the product to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure and does not meet it. 'Fetch' implies a read, but nothing is said about what happens when the ID does not exist, whether an error or empty result is returned, or any permission/rate-limit considerations.

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

Conciseness4/5

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

One short sentence, front-loaded with the verb and resource, with no filler. Minor awkwardness in 'a single product details' slightly hurts readability but nothing is wasted.

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

Completeness3/5

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

For a one-parameter lookup with no output schema and no annotations, the description is minimally adequate: it identifies the resource and the key. It is missing not-found/error behavior, which an agent would want before calling with an uncertain ID.

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 a single parameter with 100% schema description coverage ('The numeric ID of the product to retrieve'), so the schema already does the heavy lifting. The description's 'unique ID' adds no format or validation detail beyond that baseline.

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 states a specific verb ('Fetch') and resource ('product details') and adds the scope qualifier 'a single', which implicitly separates it from the sibling list tool get-products. It is clear what the tool does, though it never names or explicitly contrasts any sibling.

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: 'a single ... using its unique ID' suggests this is for one known product while get-products would cover bulk listing, but the description never states when to prefer one over the other or any prerequisites. No exclusions or alternative tools are named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.