Skip to main content
Glama

Get product

get_product
Read-onlyIdempotent

Returns one published product by name, ID or page address, or asks which match is meant. The compact answer includes the label composition, applicable reference limits, recent published prices and recorded dates where available. Use detail "full" for the country status, label verification and detailed comparisons, with age, scope and separate references for other countries. Reference data only: it does not cover medication interactions, diagnosis or treatment decisions.

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
idNoVerateca product id, e.g. "US:302778", as returned by search_products.
urlNoVerateca product page address, as an alternative to id.
detailNoCompact answer by default. Use full for the complete published record.compact
countryNoThe United States is the only market currently available.US
productNoName on the label, with brand, strength and form where known.
period_daysNoOptional days of consumption, calculated from verified pack and daily-use basis. This is not a whole-pack checkout price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds genuinely non-obvious context on top: the tool will ask which match is meant when several products match, and the response payload contents (label composition, reference limits, recent published prices, recorded dates) are summarized. The scope disclaimer further bounds what the data can be used for. Only the no-match / error path goes unstated.

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?

The purpose is front-loaded in the first sentence, with payload contents and the detail="full" rule following in logical order. The middle sentence is dense — 'applicable reference limits, recent published prices and recorded dates where available' — but every clause carries information rather than restating the title.

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 six optional parameters, no output schema and no required fields, the description does the needed work: it explains which identifiers are accepted, what the compact versus full responses contain, and what domain the data does not cover. What is missing is only the failure mode when no product matches, which is minor for a read-only lookup tool.

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 coverage is 100%, so every parameter including the detail enum is already documented, making 3 the baseline. The description does add some meaning beyond the schema by explaining what detail="full" unlocks (country status, verification, comparisons with age, scope and separate country references), but period_days and country receive no additional explanation in the description.

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 — 'Returns one published product by name, ID or page address' — and signals single-record scope, which implicitly separates it from the multi-record search_products and compare_products siblings. It stops short of naming any sibling explicitly, so it lands just below the top mark.

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 gives one concrete usage rule (use detail "full" for country status, label verification and detailed comparisons) and a clear scope exclusion ('Reference data only: it does not cover medication interactions, diagnosis or treatment decisions'). However, it never says when to prefer get_ingredient, compare_products or search_products over this tool, leaving the sibling routing to inference.

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