get_productFull detail for one Stienhardt product by id (as returned by search_inventory): title, price, availability, options, images, and the product URL on stienhardt.com.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Product id, e.g. gid://shopify/Product/123 |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds the output fields but does not disclose additional behavioral details such as not-found handling or data freshness beyond what openWorldHint already implies.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One tightly written sentence with the core action front-loaded and every phrase earning its place. It avoids redundancy and gives the agent the essential information immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter read-only retrieval tool, the description is complete: it identifies the id source, names the returned fields, and is backed by strong annotations and sibling context. No critical information needed to invoke the tool correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single id parameter is already well documented with an example. The description confirms the id comes from search_inventory but otherwise adds little beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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 detail for one Stienhardt product by id') and enumerates the returned fields. It clearly distinguishes itself from search_inventory, which is the list-level sibling tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'as returned by search_inventory' tells the agent where the required id originates and implies this tool is the follow-up detail lookup. It does not explicitly state when not to use it, but the usage context is clear and sufficient for this simple retrieval tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target clearly distinct actions: searching, fetching details, looking up terms, verifying reports. The main ambiguity is between define and dutch_marquise_definition, since the latter appears to be a single encyclopedia entry surfaced as a standalone tool.
All names are snake_case and readable, but the set mixes verb-led names like search_inventory and get_product with noun-phrase names like lab_grown_price_index and dutch_marquise_definition. The pattern is not consistent enough to predict the tool name from the action alone.
Ten tools is well within the ideal range for a server that handles both diamond education and catalog shopping. Each tool contributes to a clear workflow: learn about diamonds, search inventory, fetch product details, and verify grading reports.
The tool surface covers the main user journey: research terms, search inventory, get product detail, understand grading, and verify reports. Minor gaps exist, such as only having a dedicated definition for the Dutch Marquise cut while other shapes rely on the general encyclopedia lookup.