intent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_offersA | Find physical products that ship to a US address. Pass only what the user said: an exact product or a kind of product, any must-haves, their budget in US dollars and their 5-digit US ZIP code. Never guess a ZIP code or a budget. If the result lists missing details, ask the user only for those, then call again. US delivery only. The result ends with what this gateway sent to Intent Cloud and what it blocked. |
| create_cartA | Prepare a cart for the offer the user picked, using its offer_handle from find_offers. This does not buy anything: every purchase needs a person to approve it with a passkey, through the link or QR code in the result. Pass a quantity only if the user asked for one. US delivery only. The result ends with what this gateway sent to Intent Cloud and what it blocked. |
| get_approval_statusA | Check whether the person approved a purchase with their passkey, using the approval_handle from create_cart. Only a passkey approval the gateway verified counts as approved; tell the user what the result says. The result ends with what this gateway sent to Intent Cloud and what it blocked. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool occupies a single, distinct step in one linear flow: searching offers, preparing a cart from a chosen offer, and checking passkey approval status. The handles involved (offer_handle vs approval_handle) further separate the tools so an agent cannot easily mix them up.
All three names follow a clean verb_noun snake_case pattern: find_offers, create_cart, get_approval_status. No style drift or vague verbs.
Three tools is on the lean side, but it matches the narrow purpose of a US product checkout gateway where one step leads deterministically to the next. Nothing extraneous, though it leaves little room for supplementary operations.
The find -> create cart -> approve lifecycle is fully covered end to end, including the human passkey gate. Minor gaps like updating quantity after cart creation or cancelling/expiring a cart are absent but can be worked around by asking the user.