Zoho Inventory Connector
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZOHO_DC | Yes | Zoho data centre, e.g. 'in' for zoho.in accounts. | in |
| EVAL_API_KEY | No | Optional API key for running the LLM eval (a free Groq key works; Anthropic/Ollama via env). | |
| ZOHO_PII_MODE | No | Set to 'full' to disable masking of customer email, phone and street; otherwise PII is masked. | masked |
| ZOHO_CLIENT_ID | Yes | Your Zoho Inventory OAuth client ID from the Zoho API console. | |
| ZOHO_CONNECTION | No | Keeps one named connection per merchant org (used via --connection or ZOHO_CONNECTION). | |
| ZOHO_CLIENT_SECRET | Yes | Your Zoho Inventory OAuth client secret from the Zoho API console. | |
| ZOHO_QUOTA_UTC_OFFSET_MINUTES | No | Adjusts when the daily quota resets, since the daily quota resets at midnight IST. |
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 |
|---|---|
| list_itemsA | Browse the merchant's catalogue with stock levels (all warehouses combined). Use for overviews such as 'what is running low?'. For specific SKUs use check_availability. |
| get_itemA | Full detail for one item, including stock per warehouse/location. Give exactly one of item_id or sku. |
| search_itemsA | Find items by partial name or SKU when you do not know the exact SKU. |
| check_availabilityA | Can these SKUs be sold right now? Returns sellable yes/no with a reason per SKU (out of stock, insufficient quantity, inactive, unknown SKU). Call this before an agent pitches, recovers or promises any product to a customer. |
| list_sales_ordersA | Browse sales orders, newest first, optionally by status and order-date range. |
| search_sales_ordersA | Find sales orders by reference number, order number, customer or text. Give at least one criterion. |
| get_sales_orderA | One sales order with line items, shipped quantities, packages and (masked) customer contact. Give exactly one identifier. |
| get_fulfilment_evidenceA | Proof-of-fulfilment pack for one order: every shipment with carrier, tracking (AWB), ship and delivery dates and items, a verdict (DELIVERED, PARTIALLY_DELIVERED, SHIPPED_NOT_DELIVERED, NOT_SHIPPED, CANCELLED), a one-line factual summary and the gaps that weaken it. Use for chargebacks/disputes and 'where is my order' questions. |
| connector_statusA | Which Zoho organization is connected, granted scopes, and how much of the per-minute and daily API budget is left. Costs no Zoho API calls. |
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 9 tools
Each tool targets a distinct resource+action: availability check, catalogue browsing, single-item detail, item search, order listing, order search, single-order fetch, fulfilment evidence, and connector status. The list/search and get/list pairs are cleanly separated by explicit guidance in the descriptions (e.g. 'For specific SKUs use check_availability').
Nearly all tools follow a consistent verb_noun snake_case pattern (check_availability, list_items, get_item, search_sales_orders). The only deviation is the noun-only connector_status, which is a minor and understandable exception for a meta/status tool.
Nine tools is well-scoped for a merchant inventory/sales-order connector, with each tool earning its place and no redundant padding.
Read/lookup coverage is strong (items, availability, orders, fulfilment evidence, status), but the surface is entirely read-only: there are no tools to create or update items, adjust stock, create sales orders, or record shipments. These are notable gaps for a connector whose agents may need to act on inventory or orders, though some may be intentional scoping.