Skip to main content
Glama

3d2holo

by com.3d2holo.backend
OverviewDiscussionsAdmin

Get a 3D photo print price estimate

get_print_quote
Read-onlyIdempotent

Estimate the price of a custom physical 3D2HOLO lenticular photo print when the user asks how much a print will cost. Use this tool when the user provides or asks about print dimensions and quantity. The quote includes the applicable craft fee, lenticular grating/material fee, and shipping estimate. Use the tool for actual quote calculations instead of estimating the price from general product information. Do not use it for digital workflow questions, technical print-parameter calculations, or LPI calibration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoShipping destination country/region (optional). Shipments to foreign destinations outside mainland China, Hong Kong, Macau and Taiwan include a 60g packaging box weight in the shipping estimate; omit to estimate for a foreign destination.
widthInYesPrint width in inches (0.1-16)
heightInYesPrint height in inches (0.1-11)
quantityNoNumber of prints (1-50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / heightIn / description
      Previous value: -"Print height in inches (4-11)"New value: +"Print height in inches (0.1-11)"
    • changedInput schema / properties / heightIn / minimum
      Previous value: -4New value: +0.1
    • changedInput schema / properties / widthIn / description
      Previous value: -"Print width in inches (4-16)"New value: +"Print width in inches (0.1-16)"
    • changedInput schema / properties / widthIn / minimum
      Previous value: -4New value: +0.1
  2. Changed1 schema field changed
    • addedInput schema / properties / country
      Added value: +{
+  "description": "Shipping destination country/region (optional). Shipments to foreign destinations outside mainland China, Hong Kong, Macau and Taiwan include a 60g packaging box weight in the shipping estimate; omit to estimate for a foreign destination.",
+  "maxLength": 120,
+  "type": "string"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, closed-world safety profile, so the bar is lower. The description adds real value by enumerating what the returned quote comprises (craft fee, lenticular grating/material fee, shipping estimate) and by stating the intended use over manual estimation. It does not need to explain safety behavior.

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?

Front-loads the purpose, then usage, then quote contents, then exclusions. Every sentence carries information, though the enumeration of fee components is slightly list-like and could be tightened.

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 appropriately tells the agent what the quote includes and when the tool applies, which is enough to invoke and interpret it. Remaining gaps (numeric precision, error behavior for invalid dimensions) are minor for a read-only estimator.

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 width, height, quantity, and the country/packaging-box nuance are already fully documented in the schema. The description only names 'print dimensions and quantity' at a high level and adds no syntax or constraint detail beyond that, so it sits at the baseline.

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?

States a specific verb (estimate) and resource (price of a custom 3D2HOLO lenticular photo print), and implicitly distinguishes itself from the sibling calculation/info tools by scoping to physical print quoting. An agent can identify the tool's job without opening the schema.

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

Usage Guidelines5/5

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

Explicitly gives triggering conditions (user asks how much a print will cost, provides dimensions and quantity) and explicit exclusions (digital workflow questions, technical print-parameter calculations, LPI calibration). It also directs the agent to use this instead of estimating from general product information, which rules out the get_product_info sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All 3d2holo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources