Skip to main content
Glama
Sign In

Have It Printed

by com.haveitprinted
OverviewDiscussionsAdmin

Prepare the exact payable total

hip_prepare_payment
Idempotent

Resolve the EXACT amount HIP will charge, before any payment authorization is obtained or spent. This does NOT charge anything. Returns subtotal_cents, tax_cents, total_cents, currency, a pricing fingerprint and the authorization types HIP accepts. Tax is calculated by Stripe from the destination, so hip_quote alone is not the payable amount. The returned total is bound to this job's documents, options and recipient: change any of them and payment is refused with QUOTE_STALE until you prepare again. Use this when paying autonomously with a delegated payment authorization; a human paying in a browser does not need it. Commits the job to the autonomous payment rail.

Input Schema

NameRequiredDescriptionDefault
job_handleYes
buyer_emailNooptional: the buyer's email address. Have It Printed sends its order confirmation there once the payment succeeds.
address_confirmedNooptional, no longer needed: accepted for compatibility and ignored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / address_confirmed / description
      Previous value: -"optional: true only after ADDRESS_UNVERIFIED, when the person confirms the recipient's address is right as it is (Have It Printed checks it again after payment and holds it for a person before anything prints)."New value: +"optional, no longer needed: accepted for compatibility and ignored."
  2. Changed1 schema field changed
    • addedInput schema / properties / address_confirmed
      Added value: +{
+  "description": "optional: true only after ADDRESS_UNVERIFIED, when the person confirms the recipient's address is right as it is (Have It Printed checks it again after payment and holds it for a person before anything prints).",
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / buyer_email
      Added value: +{
+  "description": "optional: the buyer's email address. Have It Printed sends its order confirmation there once the payment succeeds.",
+  "type": "string"
+}
  4. Added
  5. Removed
  6. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false): it clarifies no charge occurs, that the call commits the job to the autonomous payment rail, and that the returned total is bound to the job's documents/options/recipient with a QUOTE_STALE refusal otherwise. This is exactly the mutation/staleness context an agent needs and it is consistent with the annotation profile.

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?

Six dense sentences, front-loaded with the key non-charge guarantee and return fields, with the use-case routing at the end. Slightly verbose in phrases like 'before any payment authorization is obtained or spent,' but almost every sentence earns its place.

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?

No output schema exists, so the description correctly enumerates the return shape (subtotal_cents, tax_cents, total_cents, currency, pricing fingerprint, accepted authorization types). Combined with the staleness/commitment semantics, nothing essential for correct invocation is missing.

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 67% and the description adds little parameter-level detail: buyer_email and address_confirmed semantics live in the schema, and job_handle is only referenced obliquely via 'this job's documents'. The valid baseline for partial coverage is a 3 since the schema carries the documented params.

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+resource ('Resolve the EXACT amount HIP will charge') and immediately distinguishes itself from the sibling hip_quote, which produces a non-payable amount because Stripe computes tax from the destination. An agent can pick 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?

Explicitly scopes usage: 'Use this when paying autonomously with a delegated payment authorization; a human paying in a browser does not need it.' It also names the alternative (hip_quote) and explains why it is insufficient. Both the when and the when-not are present.

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

All Have It Printed 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