Create a Stripe Checkout session for the job and return its URL. This does NOT take payment: the customer completes payment at that URL. Show them the quote first.
| Name | Required | Description | Default |
|---|---|---|---|
| job_handle | Yes | ||
| customer_email | No | for the receipt and tracking email |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden and does it well: it discloses the main side effect (creating a checkout session), explicitly clarifies that payment is not captured by this tool, and points to where payment actually occurs. It could add details about state changes or duplicate-session behavior, but the critical safety-relevant boundary is clearly stated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the core purpose and outcome, followed by the key negation and a workflow cue. Every sentence earns its place with no repetition or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-parameter tool with no output schema, the description provides the essential context: what it creates, what it returns, what it does not do, and the recommended preceding step. It is slightly short on edge-case or state-change details, but it is complete enough for an agent to invoke the tool correctly in the basic flow.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50%: customer_email is already documented in the schema, and the description only loosely refers to the job via 'for the job'. It does not elaborate on job_handle format or semantics, nor does it mention customer_email. The description adds minimal value beyond the schema for parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action ('Create a Stripe Checkout session'), a specific resource ('for the job'), and a concrete return value ('return its URL'). It also clearly distinguishes this tool from payment-taking siblings by explicitly saying it does NOT take payment.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear workflow context: show the quote first, create checkout, and let the customer pay at the returned URL. It does not name alternative tools explicitly, but the 'does NOT take payment' clarification and 'Show them the quote first' instruction make the intended sequencing clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.