Skip to main content
Glama

compatsy 3D printing

Get product details

get_product
Read-onlyIdempotent

Full specs with per-field confidence and source, every offer with verified time, 30/90-day price range, and the top fits per category with counts. Example: {"product_id":"prusa-mk4s"}

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
fits_limitNoFits listed per category (default 10; 0 = counts only). For one pair use check_fit
product_idYesProduct id or slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / fits_limit
      Added value: +{
      +  "description": "Fits listed per category (default 10; 0 = counts only). For one pair use check_fit",
      +  "maximum": 50,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing the returned content shape (specs with per-field confidence and source, offers with verified timestamps, price ranges, fits with counts), which matters because there is no output schema.

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?

Two compact sentences with zero filler, and the most useful information (what is returned) is front-loaded. The opening is a fragment without a verb, which slightly reduces immediate clarity about what action is performed.

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?

For a two-parameter read tool with rich annotations, the description covers the main unknown (the response contents) well, compensating for the absence of an output schema. It stops short of noting pagination on fits, error behavior for unknown ids, or how it relates to check_stock and compare.

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 100%, so the schema already documents both product_id and fits_limit, including the default of 10, the 0 = counts-only behavior, and the pointer to check_fit. The description adds only an example id value, which is marginal beyond the schema 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 enumerates exactly what comes back (full specs with confidence and source, offers with verified time, 30/90-day price range, top fits with counts), which makes the resource clear even without an explicit verb. It does not, however, distinguish this from siblings like search_products or compare, leaving the agent to infer this is the per-product detail lookup.

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?

No explicit when-to-use or when-not-to-use guidance appears in the description; the only routing hint ('For one pair use check_fit') lives in the schema for fits_limit, not the description. Usage is implied by the returned payload rather than 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.