Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

search_places

Find locations using Google Places Text Search by entering a query and optional coordinates to retrieve place information.

Instructions

Search places via Google Places Text Search

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
locationNolat,lng (optional)

Implementation Reference

  • The handler function for the "search_places" tool. Validates configuration and arguments, then invokes the GoogleMapsClient.searchPlaces method to perform the API call.
    async search_places(args: Record<string, unknown>) {
      if (!cfg.googleApiKey) throw new Error("GOOGLE_API_KEY is not configured");
      const query = String(args.query || "");
      const location = args.location ? String(args.location) : undefined;
      if (!query) throw new Error("query is required");
      return client.searchPlaces(query, location);
    },
  • Input schema defining the parameters for the search_places tool: required 'query' string and optional 'location' string.
    inputSchema: {
      type: "object",
      properties: {
        query: { type: "string" },
        location: { type: "string", description: "lat,lng (optional)" },
      },
      required: ["query"],
    },
  • Tool registration object for search_places, including name, description, and schema, within registerGoogleMaps().
    {
      name: "search_places",
      description: "Search places via Google Places Text Search",
      inputSchema: {
        type: "object",
        properties: {
          query: { type: "string" },
          location: { type: "string", description: "lat,lng (optional)" },
        },
        required: ["query"],
      },
    },
  • Top-level tool registrations array in registerAllTools(), which includes registerGoogleMaps() thereby registering the search_places tool with the MCP server.
    const registrations: ToolRegistration[] = [
      registerOpenWeather(),
      registerGoogleMaps(),
      registerNewsApi(),
      registerGitHub(),
      registerNotion(),
      registerTrello(),
      registerSpotify(),
      registerTwilio(),
      registerUnsplash(),
      registerCoinGecko(),
    ];
  • Supporting method in GoogleMapsClient class that constructs and sends the HTTP request to the Google Places Text Search endpoint.
    searchPlaces(query: string, location?: string) {
      return this.request("/maps/api/place/textsearch/json", {
        query: { query, location, key: this.apiKey },
      });
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It mentions 'Google Places Text Search' which implies an external API call, but doesn't describe rate limits, authentication needs, response format, pagination, or error behavior. The description is insufficient for a tool that likely has significant behavioral characteristics.

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 extremely concise - a single sentence with zero wasted words. It's front-loaded with the core functionality and uses efficient phrasing. Every word earns its place in communicating the essential purpose.

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?

For a search tool with no annotations, no output schema, and incomplete parameter documentation, the description is inadequate. It doesn't explain what results to expect, how they're structured, limitations of the Google Places API, or error handling. The description provides only basic functional context without the necessary operational details.

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?

With 50% schema description coverage (only 'location' has a description), the description adds no parameter information beyond what the schema provides. It doesn't explain what 'query' should contain, format examples, or constraints. The baseline is 3 since the schema covers half the parameters, but the description doesn't compensate for the undocumented 'query' parameter.

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 action ('Search') and resource ('places via Google Places Text Search'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'geocode_address' or 'search_photos', but the specific 'Google Places Text Search' context provides reasonable distinction.

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 like 'geocode_address' or other search tools. There's no mention of prerequisites, limitations, or appropriate use cases beyond the basic function stated.

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/TaylorChen/muti-mcps'

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