getir-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GETIR_TOKEN | Yes | Bearer token from Getir partner portal |
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 |
|---|---|
| list_ordersC | List orders from your Getir store |
| get_orderA | Get a specific order by ID |
| accept_orderC | Accept an incoming order |
| reject_orderB | Reject an incoming order |
| list_productsB | List products in your Getir store |
| update_product_availabilityB | Enable or disable a product |
| update_product_priceC | Update product price |
| get_store_statusA | Get current store status (open/busy) |
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 8 tools
Each tool targets a distinct resource and action: orders (list, get, accept, reject), products (list, update availability, update price), and store status (get). No two tools overlap in purpose, so an agent can clearly distinguish them.
All tool names follow a consistent verb_noun pattern in snake_case: list_orders, get_order, accept_order, reject_order, list_products, update_product_availability, update_product_price, get_store_status. This makes the set predictable and easy to navigate.
With 8 tools, the set is well-scoped for a Getir store management server. It covers orders, products, and store status without unnecessary redundancy or bloat.
The tool set covers the core workflows for managing orders (list, get, accept, reject) and products (list, update price, update availability). However, there is no way to update store status (e.g., open/close), which is a minor gap in lifecycle coverage.