Ship Receipt
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHIP_RECEIPT_URL | No | URL of the web tool shown in the receipt reply. | https://ship-receipt.kevinssue.workers.dev |
| SHIP_RECEIPT_PORT | No | Port used when running in HTTP mode. | 8080 |
| SHIP_RECEIPT_OUTPUT_DIR | No | Also save each PNG to this folder (stdio use). | |
| SHIP_RECEIPT_SITE_LABEL | No | Watermark label shown on the receipt. | Ship Receipt |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_receiptA | Print a 1200x675 'launch receipt' PNG for a product launch (visits, signups, revenue, cost) with an honest verdict (PROFITABLE, PRE-REVENUE, TUITION PAID, BREAK-EVEN, EXPERIMENT). Returns the image inline so the user can save it or post it on X. Numbers are self-reported by the user and the receipt says so. Nothing is stored or sent anywhere. |
| describe_ship_receiptA | Explain what Ship Receipt is, which fields a receipt takes, the paper styles, and the privacy model. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: generate_receipt produces an image, while describe_ship_receipt provides explanatory documentation. An agent can easily tell which to call based on whether the user wants output or information.
Both tools use consistent snake_case with a verb_noun structure (generate_receipt, describe_ship_receipt). The inclusion of the server name in describe_ship_receipt is a harmless, readable variation.
Only two tools exist, which is slightly thin but justified by the narrow, single-purpose scope of generating a launch receipt PNG. The describe tool complements the generator without adding unnecessary surface area.
The domain is fully covered: one tool generates the receipt and the other explains fields, styles, and privacy. Since nothing is stored, CRUD operations are not needed, and there are no obvious dead ends.