Skip to main content
Glama

Price a stamp from its size

calculate_stamp_price
Read-only

Calculate the price of a custom concrete stamp from its outer dimensions. Uses the same formula as checkout. Dimensions are in inches, each at least 6", with one side 46" or less and the other 94" or less. Plates are cut in whole inches, so a fractional size is quoted (and returned) rounded up. When you have the words rather than a size, call quote_inscription instead: the size comes from the lettering. Excludes shipping and 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": {
      "width_inches": "<width_inches>",
      "height_inches": "<height_inches>"
    },
    "name": "calculate_stamp_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityNo
width_inchesYesStamp width in inches. The stamp must have one side 46" or less and the other 94" or less.
height_inchesYesStamp height in inches. The stamp must have one side 46" or less and the other 94" or less.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely useful behavior: it uses the same formula as checkout, rounds fractional sizes up because plates are cut in whole inches, and excludes shipping and tax. It stops short of describing the shape of the returned price (currency, whether quantity multiplies the figure), which matters given 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.

Conciseness5/5

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

Five tight sentences, front-loaded with the core action, then constraints, then rounding behavior, then the sibling routing rule. No filler or restatement of the title.

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 read-only pricing calculator with no output schema, the description covers the formula provenance, dimensional limits, rounding rule, and exclusions. The only meaningful omission is what the returned price represents relative to the quantity parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the description compensates with a cross-field constraint the schema cannot express: each side at least 6", with one side 46" or less and the other 94" or less. The remaining gap is quantity, which appears in the schema with a default and bounds but no explanation of whether it multiplies the quoted price.

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 and resource ('Calculate the price of a custom concrete stamp from its outer dimensions') and immediately distinguishes itself from the sibling quote_inscription by naming the case where that tool applies. An agent can route between the two without opening either 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?

Gives explicit when-to-use guidance ('when you have the words rather than a size, call quote_inscription instead') and explains why the alternative is needed ('the size comes from the lettering'). It also states what the tool excludes (shipping and tax), so the agent knows not to expect a full order total.

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