Skip to main content
Glama
DumplingAI

Dumpling AI MCP Server

Official
by DumplingAI

search-places

Find detailed business information by searching for places using location, country, and language parameters.

Instructions

Search for places with detailed business information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query
countryNoCountry code (e.g., 'us')
locationNoLocation name
languageNoLanguage code (e.g., 'en')
pageNoPage number

Implementation Reference

  • The handler function for the 'search-places' tool. It proxies the request to the Dumpling AI API endpoint /api/v1/search-places, authenticates with DUMPLING_API_KEY, and returns the JSON response as text content.
    async ({ query, country, location, 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-places`, {
        method: "POST",
        headers: {
          "Content-Type": "application/json",
          Authorization: `Bearer ${apiKey}`,
        },
        body: JSON.stringify({ query, country, location, 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 input schema for the 'search-places' tool defining parameters: query (required string), and optional country, location, language (strings), page (number).
    {
      query: z.string().describe("Search query"),
      country: z.string().optional().describe("Country code (e.g., 'us')"),
      location: z.string().optional().describe("Location name"),
      language: z.string().optional().describe("Language code (e.g., 'en')"),
      page: z.number().optional().describe("Page number"),
    },
  • src/index.ts:207-233 (registration)
    The complete registration of the 'search-places' tool using McpServer.tool method, including name, description, input schema, and handler function.
    server.tool(
      "search-places",
      "Search for places with detailed business information.",
      {
        query: z.string().describe("Search query"),
        country: z.string().optional().describe("Country code (e.g., 'us')"),
        location: z.string().optional().describe("Location name"),
        language: z.string().optional().describe("Language code (e.g., 'en')"),
        page: z.number().optional().describe("Page number"),
      },
      async ({ query, country, location, 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-places`, {
          method: "POST",
          headers: {
            "Content-Type": "application/json",
            Authorization: `Bearer ${apiKey}`,
          },
          body: JSON.stringify({ query, country, location, 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 (despite having a 'page' parameter), or what 'detailed business information' specifically includes.

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 at just one sentence with no wasted words. It's front-loaded with the core purpose and efficiently communicates the essential function. Every word earns its place in this minimal description.

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 5 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't address what the tool returns, how results are structured, whether there are limitations or constraints, or how it differs from similar search tools on the server. 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?

With 100% schema description coverage, the input schema already documents all 5 parameters adequately. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters (e.g., how 'country' and 'location' interact), provide examples of effective queries, or clarify what 'detailed business information' means in the context of these parameters.

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 for places with detailed business information,' which specifies the verb (search), resource (places), and type of information returned (detailed business information). However, it doesn't differentiate from sibling tools like 'search-maps' or 'search,' leaving some ambiguity about when to use this specific place search tool versus other search tools.

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-maps' and 'search' available, there's no indication of what makes this place search tool distinct or when it should be preferred over other search capabilities on the server.

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