Skip to main content
Glama

Get a product's options

get_product
Read-onlyIdempotent

The whole option form for one Printdash product, as its product page offers it: every field in the order to ask, whether it is required, each option's id and label, defaults, quantity and custom size limits, page counts, what is applied automatically, which stocks a finish is priced on, the product image, the artwork guides that apply, and default_configuration (the page's starting job, ready for price_job). Read this before asking the customer anything. Printdash prints in Australia and delivers within Australia only; prices are in AUD and include GST.

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_idYesA product id from list_products or search_products.

Output Schema

NameRequiredDescriptionDefault
urlYes
nextYes
fieldsYes
bindingYes
designsNo
productYes
currencyYes
templateYes
image_urlYes
product_idYes
descriptionYes
service_areaYes
option_matrixYes
artwork_guidesYes
prices_include_gstYes
default_configurationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / applied_automatically
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "service_area",
      -  "currency",
      -  "prices_include_gst",
      -  "product_id",
      -  "product",
      -  "description",
      -  "url",
      -  "image_url",
      -  "template",
      -  "binding",
      -  "fields",
      -  "applied_automatically",
      -  "option_matrix",
      -  "default_configuration",
      -  "artwork_guides",
      -  "next"
      -]New value: +[
      +  "service_area",
      +  "currency",
      +  "prices_include_gst",
      +  "product_id",
      +  "product",
      +  "description",
      +  "url",
      +  "image_url",
      +  "template",
      +  "binding",
      +  "fields",
      +  "option_matrix",
      +  "default_configuration",
      +  "artwork_guides",
      +  "next"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real context: the payload is a complete snapshot suitable for driving a customer conversation, it chains into price_job, and it discloses domain constraints (Australia-only delivery, AUD prices including GST). It does not discuss failure modes for an unknown product_id, which keeps it at 4.

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

Conciseness3/5

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

Purpose and the usage directive are front-loaded, which is good, but the middle of the description is one long comma-chained enumeration of return fields that the output schema already declares. That listing is redundant bulk an agent does not need from prose. The closing compliance sentence does earn its place.

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 a dedicated output schema, the return values need not be spelled out, and the description instead supplies what the schema cannot: workflow position (read before asking the customer), the downstream hand-off to price_job, and commercial constraints (Australia, AUD incl GST). Nothing essential to correct invocation is missing.

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% and the single parameter is already documented as 'A product id from list_products or search_products', so the schema does the heavy lifting. The description only implies a specific existing product ('one Printdash product') and adds no format or validation detail beyond that. Baseline 3 applies.

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 opens with a specific verb-and-resource: it returns the whole option form for one Printdash product, and it enumerates the concrete contents (fields in ask order, required flags, option ids/labels, defaults, quantity and size limits). The phrase 'one Printdash product' also scopes it against the list_products/search_products siblings, which return collections. An agent can tell immediately this is the per-product detail call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Read this before asking the customer anything' is an explicit precondition that tells the agent exactly where this sits in the workflow. The mention that default_configuration is the page's starting job 'ready for price_job' routes the agent to the logical next tool. It lacks an explicit when-not-to-use or a named alternate, keeping it just short of a 5.

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