Skip to main content
Glama
Sign In

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 craft fee, lenticular grating/material fee, and shipping estimate, computed from current pricing rather than recalled from memory. Scope: physical print pricing only; the tool does not answer workflow, print-parameter, or calibration questions.

Input Schema

NameRequiredDescriptionDefault
countryNoShipping destination country/region (optional). Shipments to foreign destinations outside mainland China, Hong Kong, Macau and Taiwan include a 100g 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-2000); checkout caps it per size/destination by the PayPal $10k per-transaction limit

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / quantity / description
      Previous value: -"Number of prints (1-50)"New value: +"Number of prints (1-2000); checkout caps it per size/destination by the PayPal $10k per-transaction limit"
    • changedInput schema / properties / quantity / maximum
      Previous value: -50New value: +2000
  2. Changed1 schema field changed
    • changedInput schema / properties / country / description
      Previous value: -"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."New value: +"Shipping destination country/region (optional). Shipments to foreign destinations outside mainland China, Hong Kong, Macau and Taiwan include a 100g packaging box weight in the shipping estimate; omit to estimate for a foreign destination."
  3. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. 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
  5. 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"
+}
  6. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: the quote includes craft fees, lenticular grating/material fees, and a shipping estimate, and it is computed from current pricing rather than recalled from memory.

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 description is front-loaded with purpose and follows with usage conditions and scope exclusions. It is generally efficient, with only minor repetition between 'when the user asks how much a print will cost' and 'when the user provides or asks about print dimensions and quantity.'

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 moderate-complexity pricing tool with four parameters and full schema coverage, the description gives enough context to invoke it correctly. It explains the fee components included in the quote and the scope, though without an output schema it could be slightly clearer about the exact return structure.

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 all four parameters are already well documented. The description only reinforces that print dimensions and quantity are relevant inputs, without adding syntax, constraints, or meaning beyond the schema; baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource: 'Estimate the price of a custom physical 3D2HOLO lenticular photo print.' It also distinguishes the tool from siblings by scoping it to physical print pricing and explicitly excluding workflow, print-parameter, and calibration questions, so an agent can tell when this tool is appropriate.

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?

It gives clear when-to-use conditions: 'when the user asks how much a print will cost' and 'when the user provides or asks about print dimensions and quantity.' The scope statement also provides when-not guidance by excluding workflow, print-parameter, and calibration topics, though it does not name specific alternative tools.

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