Tally MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TALLY_TOKEN | No | Default bearer token for Tally API. | |
| TALLY_API_KEY | No | API key (default 3C9DEDE2-EC3E-43E3-9C20-E591ED341127). | |
| TALLY_BASE_URL | No | Base URL for Tally API (default https://tally.prod.readytouchpos.com). | |
| TALLY_PAGE_SIZE | No | Default page size for product paging (default 100). | |
| TALLY_ACCOUNT_ID | No | Default account ID. | |
| TALLY_LOCATION_ID | No | Default location ID (e.g., 4dfd336941716947dba20acffc45660d). |
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 |
|---|---|
| set_tally_tokenA | Set or update the Tally bearer token used by other tools. |
| list_categoriesC | List product categories available for a location. |
| list_productsC | Retrieve products with optional category/search/price filters. |
| ask_productsC | Answer natural-language questions about products/prices by querying Tally data. |
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
set_tally_token and list_categories are clearly distinct from the other tools. list_products and ask_products both retrieve product data, so they could be confused, but their descriptions separate structured filtering from natural-language querying.
Most tool names follow a clear verb_noun snake_case pattern: set_tally_token, list_categories, list_products. ask_products deviates slightly from the action style but remains readable and consistent with the overall convention.
Four tools form a compact, focused server for exploring and querying product/category data. The count is small but appropriate for a read-oriented Tally integration, and each tool has a clear role.
The set covers authentication, category listing, product listing/filtering, and natural-language product questions, which covers the core query workflow. Some gaps exist, such as no explicit product detail-by-ID or location-listing tool, but agents can likely work around these.