Skip to main content
Glama

Get product details

get_product
Read-onlyIdempotent

Full public details of one product: specs, models, documents, FAQ, price/availability. Pass slug or the 6-digit code.

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

Input Schema

NameRequiredDescriptionDefault
codeNo
slugNo
localeNoContent language: en, fa, ar or ckb.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds useful scope by calling the data 'public' and listing content categories, though it does not address rate limits or what happens when no identifier is supplied.

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 compact sentences with no filler; the content scope is front-loaded and the identifier guidance follows immediately. Every phrase contributes useful 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 no output schema, the description usefully enumerates the returned data categories (specs, models, documents, FAQ, price/availability) and identifier options. Minor gaps remain around locale effects and the zero-required-parameter edge case.

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 only 33%, and the description partially compensates by stating that `code` is 6-digit and that `slug` or `code` can identify the product. However, it leaves locale behavior, conflict/precedence rules, and the both/neither identifier case unaddressed.

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 states a specific verb and resource ('Full public details of one product') and enumerates the kinds of details returned. The singular 'one product' scope distinguishes it from list/search siblings such as search_products and list_resources.

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?

It implies use when full details for a known product are needed and gives identifier options, but it does not explicitly name alternatives like search_products or say when not to use this tool. No prerequisites or exclusions are stated.

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