Skip to main content
Glama
DumplingAI

Dumpling AI MCP Server

Official
by DumplingAI

search-maps

Find locations and businesses on Google Maps using search queries, GPS coordinates, or place identifiers within the Dumpling AI MCP Server.

Instructions

Search Google Maps for locations and businesses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query
gpsPositionZoomNoGPS coordinates with zoom (e.g., 'lat,long,zoom')
placeIdNoGoogle Place ID
cidNoGoogle Maps CID
languageNoLanguage code (e.g., 'en')
pageNoPage number

Implementation Reference

  • The handler function that executes the tool logic by making an API call to Dumpling AI's search-maps endpoint with the provided parameters.
    async ({ query, gpsPositionZoom, placeId, cid, language, page }) => {
      const apiKey = process.env.DUMPLING_API_KEY;
      if (!apiKey) throw new Error("DUMPLING_API_KEY not set");
      const response = await fetch(`${NWS_API_BASE}/api/v1/search-maps`, {
        method: "POST",
        headers: {
          "Content-Type": "application/json",
          Authorization: `Bearer ${apiKey}`,
        },
        body: JSON.stringify({
          query,
          gpsPositionZoom,
          placeId,
          cid,
          language,
          page,
        }),
      });
      if (!response.ok)
        throw new Error(`Failed: ${response.status} ${await response.text()}`);
      const data = await response.json();
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Zod schema defining the input parameters for the search-maps tool, including query, optional GPS position, place ID, CID, language, and page.
    {
      query: z.string().describe("Search query"),
      gpsPositionZoom: z
        .string()
        .optional()
        .describe("GPS coordinates with zoom (e.g., 'lat,long,zoom')"),
      placeId: z.string().optional().describe("Google Place ID"),
      cid: z.string().optional().describe("Google Maps CID"),
      language: z.string().optional().describe("Language code (e.g., 'en')"),
      page: z.number().optional().describe("Page number"),
    },
  • src/index.ts:167-204 (registration)
    Registers the 'search-maps' tool with the MCP server using server.tool(), providing name, description, input schema, and handler function.
    server.tool(
      "search-maps",
      "Search Google Maps for locations and businesses.",
      {
        query: z.string().describe("Search query"),
        gpsPositionZoom: z
          .string()
          .optional()
          .describe("GPS coordinates with zoom (e.g., 'lat,long,zoom')"),
        placeId: z.string().optional().describe("Google Place ID"),
        cid: z.string().optional().describe("Google Maps CID"),
        language: z.string().optional().describe("Language code (e.g., 'en')"),
        page: z.number().optional().describe("Page number"),
      },
      async ({ query, gpsPositionZoom, placeId, cid, language, page }) => {
        const apiKey = process.env.DUMPLING_API_KEY;
        if (!apiKey) throw new Error("DUMPLING_API_KEY not set");
        const response = await fetch(`${NWS_API_BASE}/api/v1/search-maps`, {
          method: "POST",
          headers: {
            "Content-Type": "application/json",
            Authorization: `Bearer ${apiKey}`,
          },
          body: JSON.stringify({
            query,
            gpsPositionZoom,
            placeId,
            cid,
            language,
            page,
          }),
        });
        if (!response.ok)
          throw new Error(`Failed: ${response.status} ${await response.text()}`);
        const data = await response.json();
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
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. While 'search' implies a read-only operation, the description doesn't address important behavioral aspects like rate limits, authentication requirements, result format, pagination behavior, or whether this is a real-time search versus cached data. For a search tool with 6 parameters and no annotation coverage, this is inadequate.

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 that gets straight to the point. There's no wasted language or unnecessary elaboration. It's front-loaded with the core functionality and doesn't bury important information.

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 6 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what kind of results to expect, how results are structured, whether there are limitations or quotas, or how to interpret the various search parameters. The agent would need to guess about important operational aspects.

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?

Schema description coverage is 100%, so the schema already documents all 6 parameters thoroughly. The description doesn't add any meaningful parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters (e.g., how 'gpsPositionZoom' affects results) or provide usage examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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: 'Search Google Maps for locations and businesses.' It specifies the verb ('search'), resource ('Google Maps'), and target ('locations and businesses'). However, it doesn't differentiate from sibling tools like 'search-places' or 'search', which might have overlapping functionality.

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-places' and 'search' available, there's no indication of what makes this tool distinct or when it should be preferred over those options. No exclusions or prerequisites are mentioned.

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/DumplingAI/mcp-server-dumplingai'

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