Turbify Store MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TURBIFY_STORE_ID | Yes | Your Turbify Store ID | |
| TURBIFY_CONTRACT_TOKEN | Yes | Your Turbify contract token for API authentication |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_catalog_itemsB | |
| search_catalog_itemsA | |
| advanced_search_catalog_itemsB | |
| create_itemsB | |
| update_itemsC | |
| delete_itemsB | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| turbify_store_api_docs | Documentation for the Turbify Store Catalog API |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no ambiguity: advanced_search_catalog_items and search_catalog_items are explicitly differentiated in their descriptions, while create_items, get_catalog_items, update_items, and delete_items form a clean CRUD pattern. The descriptions clearly explain when to use each tool, preventing misselection.
All tools follow a consistent verb_noun pattern with snake_case throughout: advanced_search_catalog_items, create_items, delete_items, get_catalog_items, search_catalog_items, and update_items. The naming is predictable and follows the same structural convention across all six tools.
Six tools is well-scoped for a catalog/items management server. The set covers core CRUD operations plus both simple and advanced search capabilities, with each tool earning its place. This is neither too sparse nor bloated for the domain of managing a store catalog.
The tool surface provides complete CRUD lifecycle coverage for catalog items (create, get, update, delete) plus comprehensive search functionality with both simple and advanced options. There are no obvious gaps or dead ends for agents working with this catalog management domain.