Skip to main content
Glama

Have It Printed

by com.haveitprinted

hip_complete_payment

Pay for the job with a delegated payment authorization, with no browser and no human step. payment_authorization must be a Stripe shared payment token (spt_...) granted to Have It Printed whose maximum is at least the total from hip_prepare_payment; HIP charges exactly that total and never more. NEVER send a card number, expiry, CVV or any reusable credential to this tool. If the cardholder's bank requires authentication, this returns payment_status=requires_user_action rather than bypassing it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_handleYes
payment_authorizationYesopaque delegated payment token (spt_...)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses exact-charge behavior, no-human/no-browser execution, the requires_user_action fallback instead of bypassing authentication, and the prohibition on reusable credentials.

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?

Every sentence earns its place: purpose, precondition, and security/edge-case behavior are packed into four sentences with no filler. The most decision-relevant information is front-loaded.

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?

For a two-parameter payment completion tool with no output schema, the description covers everything an agent needs before calling: token requirements, charge amount, bank-auth failure mode, and what not to pass. No critical precondition appears omitted.

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 only 50% because job_handle has no description. The description compensates substantially for payment_authorization by defining token type, issuer, required maximum, and charging behavior. job_handle is only implied via 'the job' and reference to hip_prepare_payment, leaving a small inferential gap.

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?

Begins with specific verb 'Pay' and resource 'the job', and immediately specifies mechanism: delegated payment authorization, no browser, no human step. It also references hip_prepare_payment, distinguishing it from sibling payment workflow tools.

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?

States explicit preconditions: payment_authorization must be an spt_ token granted to Have It Printed with a maximum covering the hip_prepare_payment total, and HIP charges exactly that total. Also provides strong when-not guidance: never send card data and do not bypass bank authentication.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools are clearly distinct by resource and action, such as create_job vs update_job or complete_payment vs create_checkout. However, hip_quote and hip_prepare_payment both return pricing information and could be confused at first glance; the descriptions do clarify their different purposes, but an explicit warning is needed to keep them apart.

Naming Consistency5/5

All tools follow the same hip_ prefix with verb_noun snake_case naming, such as hip_create_job, hip_get_order, and hip_complete_payment. This makes the toolset predictable and easy to navigate.

Tool Count5/5

Ten tools is well-scoped for a print-and-mail service. Each tool covers a necessary part of the workflow—job creation, document upload, quoting, payment, and order tracking—without unnecessary duplication or bloat.

Completeness4/5

The core lifecycle is well covered: create and update a job, upload documents, quote, pay via autonomous or checkout flows, check payment status, and retrieve order tracking. Minor gaps exist, such as no explicit cancel/delete job or a pre-payment job status retrieval tool, but agents can likely work around these.

Resources