Skip to main content
Glama

search_places

Find specific places like restaurants or businesses in any location by entering a search query.

Instructions

Search places in a given location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchYesPlaces to search. Ex: italian restaurants in New York City, US

Implementation Reference

  • Handler logic for the 'search_places' tool. Extracts the 'search' parameter from arguments, performs a POST request to the Voyp API endpoint 'places/search', and returns the JSON-stringified response or an error message.
    } else if (request.params.name === "search_places") {
    
        // if (!isValidForecastArgs(request.params.arguments)) {
        //     throw new McpError(
        //         ErrorCode.InvalidParams,
        //         "Invalid forecast arguments"
        //     );
        // }
    
        const search = request.params.arguments?.search;
    
        try {
            const response = await this.axiosInstance.post<StartCallResponse>(API_CONFIG.ENDPOINTS.PLACES, {
                search
            });
    
            return {
                content: [{
                    type: "text",
                    text: JSON.stringify(response.data)
                }]
            };
        } catch (error) {
            if (axios.isAxiosError(error)) {
                return {
                    content: [{
                        type: "text",
                        text: `Voyp API error: ${error.response?.data.message ?? error.message}`
                    }],
                    isError: true,
                }
            }
            throw error;
        }
  • src/index.ts:243-256 (registration)
    Registration of the 'search_places' tool in the ListToolsRequestSchema handler, defining its name, description, and input schema requiring a 'search' string.
    {
        name: "search_places",
        description: "Search places in a given location",
        inputSchema: {
            type: "object",
            properties: {
                search: {
                    type: "string",
                    description: "Places to search. Ex: italian restaurants in New York City, US"
                }
            },
            required: ["search"]
        }
    },
  • Input schema definition for the 'search_places' tool, specifying an object with a required 'search' string property.
    inputSchema: {
        type: "object",
        properties: {
            search: {
                type: "string",
                description: "Places to search. Ex: italian restaurants in New York City, US"
            }
        },
        required: ["search"]
    }
  • API endpoint configuration for the places search: 'places/search'.
    PLACES: 'places/search',
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Search') but doesn't cover critical aspects like whether this is a read-only operation, potential rate limits, authentication needs, or what the search results might include (e.g., format, pagination). This is a significant gap for a search tool with zero annotation coverage.

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 a single, efficient sentence ('Search places in a given location') that is front-loaded and wastes no words. It directly communicates the core function without unnecessary elaboration, earning a perfect score for conciseness.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the search returns (e.g., list of places, details), how results are structured, or any behavioral traits like error handling. For a search tool with no structured support, this leaves the agent under-informed.

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

Parameters3/5

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

The input schema has 100% description coverage, with the 'search' parameter documented as 'Places to search. Ex: italian restaurants in New York City, US.' The description adds no additional meaning beyond this, as it doesn't elaborate on syntax or constraints. With high schema coverage, the baseline score of 3 is appropriate.

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

Purpose4/5

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

The description clearly states the tool's purpose as 'Search places in a given location,' which includes a specific verb ('Search') and resource ('places'). However, it doesn't explicitly differentiate from sibling tools like 'search_place' or 'search_place_by_number,' which appear to be similar search operations, preventing a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'search_place' and 'search_place_by_number' available, there is no indication of context, prerequisites, or exclusions, leaving the agent to guess based on tool names alone.

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/paulotaylor/voyp-mcp'

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