rush-gift-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port number for the server | 8000 |
| FASTMCP_HOST | No | Host address to bind the server | 127.0.0.1 |
| MCP_TRANSPORT | No | Transport mode for the MCP server (e.g., streamable-http) | streamable-http |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| plan_rush_giftA | Plans a last-minute gift pickup with Oda Juwotda(오다 주웠다). Use this tool whenever the user gives an origin, a destination, and the minutes left before a meeting. It returns everything in one call: gift recommendations, pickup stores near the destination, detour travel time, whether the user can still arrive on time, and a short gift message. If the user mentions a route or a meeting time, call this tool instead of recommend_gifts. |
| recommend_giftsA | Recommends gift ideas with Oda Juwotda(오다 주웠다) — ideas only. Returns gift candidates matched to relationship, occasion, budget, preferences, and constraints. It does not compute pickup stores or travel time. If origin, destination, or remaining minutes are available, call plan_rush_gift instead of this tool. |
| find_pickup_optionsA | Finds pickup stores and detour times with Oda Juwotda(오다 주웠다) for gifts that are already chosen (gift_ids). Use this as a follow-up after narrowing candidates with recommend_gifts. When origin, destination, and remaining time are all known from the start, plan_rush_gift alone is enough. |
| draft_gift_messageA | Drafts a short gift card message with Oda Juwotda(오다 주웠다) that fits the gift, relationship, occasion, and tone. |
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 4 tools
The four tools are clearly separated by intent: drafting a message, planning a full rush-gift pickup, recommending gift ideas, and finding pickup options for chosen gifts. plan_rush_gift is the comprehensive workflow, while the others are targeted components, and the descriptions explicitly state when each should be used instead of overlapping alternatives.
All tool names follow a consistent verb_noun snake_case pattern: draft_gift_message, plan_rush_gift, recommend_gifts, find_pickup_options. The verbs clearly express the action and the nouns make the target object obvious.
Four tools is a well-scoped size for this niche domain. Each tool covers a distinct stage of the workflow without bloat, and plan_rush_gift earns its place as a combined entry point for full-information scenarios.
The tool set covers the full rush-gift workflow: gift idea generation, pickup logistics, travel feasibility, and gift message drafting. plan_rush_gift aggregates the complete path, while the standalone tools handle partial-information cases, leaving no obvious dead ends.