Skip to main content
Glama
benpeke

Turbify Store MCP Server

by benpeke

search_catalog_items

Search for items in the Turbify Store catalog by matching keywords against ID, name, or code fields. Use this tool to find specific catalog items with basic search parameters.

Instructions

    Search for items in the Turbify Store catalog.
    Note: This simple search only matches the keyword against item ID, name, or code fields.
    For more advanced search capabilities against other fields, use advanced_search_catalog_items.
    
    Args:
        keyword: Search keyword (matches against ID, name, or code fields only)
        start_index: Starting index for pagination (default: 1)
        end_index: Ending index for pagination (default: 100, max: 1000)
    
    Returns:
        JSON string with search results
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYes
start_indexNo
end_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'search_catalog_items' tool. It uses TurbifyStoreAPIClient.simple_search to query the catalog by keyword within a paginated range and returns a JSON-formatted response with item IDs or errors.
    @mcp.tool()
    def search_catalog_items(
        keyword: str,
        start_index: int = 1,
        end_index: int = 100
    ) -> str:
        """
        Search for items in the Turbify Store catalog.
        Note: This simple search only matches the keyword against item ID, name, or code fields.
        For more advanced search capabilities against other fields, use advanced_search_catalog_items.
        
        Args:
            keyword: Search keyword (matches against ID, name, or code fields only)
            start_index: Starting index for pagination (default: 1)
            end_index: Ending index for pagination (default: 100, max: 1000)
        
        Returns:
            JSON string with search results
        """
        if end_index > 1000:
            end_index = 1000
    
        try:
            response = client.simple_search(keyword, start_index, end_index)
            
            # Extract item IDs from the response
            item_ids = response.item_ids if response.item_ids else []
            
            return json.dumps({
                "status": response.status,
                "success": response.is_success,
                "messages": response.success_messages,
                "errors": response.error_messages,
                "keyword": keyword,
                "start_index": start_index,
                "end_index": end_index,
                "total_items": len(item_ids),
                "item_ids": item_ids
            }, indent=2)
            
        except APIError as e:
            return json.dumps({
                "status": "error",
                "success": False,
                "errors": [str(e)],
                "keyword": keyword
            }, indent=2)
  • Top-level registration of catalog tools (including search_catalog_items) by calling register_catalog_tools on the MCP server instance in the setup_server function.
    register_catalog_tools(mcp)
  • Type hints and docstring defining the input schema (parameters: keyword (str), start_index (int=1), end_index (int=100)) and output (str JSON).
    def search_catalog_items(
        keyword: str,
        start_index: int = 1,
        end_index: int = 100
    ) -> str:
        """
        Search for items in the Turbify Store catalog.
        Note: This simple search only matches the keyword against item ID, name, or code fields.
        For more advanced search capabilities against other fields, use advanced_search_catalog_items.
        
        Args:
            keyword: Search keyword (matches against ID, name, or code fields only)
            start_index: Starting index for pagination (default: 1)
            end_index: Ending index for pagination (default: 100, max: 1000)
        
        Returns:
            JSON string with search results
        """
  • The registration helper function that defines and registers the search_catalog_items tool (and others) using @mcp.tool() decorators, sharing a TurbifyStoreAPIClient instance.
    def register_catalog_tools(mcp):
        """Register catalog management tools with the MCP server."""
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the search behavior (keyword matching against specific fields), pagination behavior with defaults and limits, and return format ('JSON string with search results'). It doesn't mention rate limits, authentication requirements, or error conditions, but provides solid operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently structured with a clear purpose statement, usage guidance, parameter documentation, and return information - all in just 7 lines. Every sentence adds value, and the information is front-loaded with the most important details first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (search with pagination), no annotations, and the presence of an output schema, the description provides strong contextual coverage. It explains the search scope, parameter semantics, pagination behavior, and return format. The main gap is lack of information about authentication, rate limits, or error handling, but the output schema reduces the need to describe return values in detail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining all three parameters: 'keyword' (what it matches against), 'start_index' (pagination starting point with default), and 'end_index' (pagination ending point with default and max). The description adds meaningful context beyond what the bare schema provides about parameter purposes and constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Search for items') and resource ('Turbify Store catalog'), and explicitly distinguishes this tool from its sibling 'advanced_search_catalog_items' by noting this is a 'simple search' with limited field matching. This provides excellent differentiation from alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool ('simple search only matches keyword against item ID, name, or code fields') and when to use an alternative ('For more advanced search capabilities against other fields, use advanced_search_catalog_items'). This gives clear context for tool selection among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/benpeke/turbify_store_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server