Skip to main content
Glama

Quote a stamp from its words

quote_inscription
Read-only

Price a custom concrete stamp from the words on it. Send the lines (and optionally a font and letter height); get back the measured stamp size in inches, the exact price (the same measurement and rounding the designer and checkout use), a standard shipping estimate, how far ahead of a pour to order, any problems that would stop the order, and design_url: a link that opens exactly this design in the free 3D designer, where the person orders it. Excludes tax.

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": {
      "lines": "<lines>"
    },
    "name": "quote_inscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
fontNoFont key; default arial-rounded (the designer's default)
linesYesThe stamp's words, one array entry per line (1-8 lines, each at most 60 characters). An empty string is a blank line.
depth_inchesNoImpression depth in inches: 0.25 (standard, the default) or 0.125 for cities that specify a 1/8" impression. Same price.
letter_height_inchesNoCapital-letter height in inches. Omit to use the designer's default (1.75"), stepped down in 0.25" steps to the font's floor if the stamp wouldn't otherwise have one side 46" or less and the other 94" or less.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, yet the description still adds real value: pricing parity with the designer and checkout, tax exclusion, a shipping estimate, an ordering lead time, and validation problems that block the order. It also clarifies that design_url is where the person orders, so the tool itself does not transact. Minor gaps remain around shipping-estimate scope and any rate limits.

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 purpose is front-loaded in the first sentence and every subsequent clause enumerates a distinct return element rather than padding. It is a dense run-on list, but the density is informative rather than wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the return contract and does so thoroughly: measured size, exact price, shipping estimate, lead time, blocking problems, and the designer link, plus the tax exclusion. For a read-only quoting tool with fully documented parameters, an agent has enough to call it and interpret the result correctly.

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%, so font keys, line limits, depth options, and the letter-height stepping rule are already documented in the schema. The description only restates that lines are required and font/letter height optional, adding essentially no meaning beyond the structured fields, which matches the baseline for full coverage.

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?

States a specific verb and resource: "Price a custom concrete stamp from the words on it," which is concrete enough for an agent to distinguish a quote-by-text tool from template search or order tracking. It does not explicitly contrast with the sibling calculate_stamp_price, leaving a small ambiguity about which pricing path to pick.

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?

It implies the use case (get a price and a designer link before ordering) and names the optional inputs, but never states when to prefer this over calculate_stamp_price or what input conditions would make it inappropriate. The guidance is inferable rather than explicit, with no when-not conditions.

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