Skip to main content
Glama
tanish-kr

mcp-server-zipcode-jp

by tanish-kr

search_zip_code

Search for Japanese addresses by entering a 7-digit zip code.

Instructions

Search zip code data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipCodeYes

Implementation Reference

  • src/index.ts:11-38 (registration)
    Tool 'search_zip_code' is registered via server.registerTool with a Zod inputSchema (zipCode: z.string()), description, and an async handler that calls the fetcher and formats the response.
    server.registerTool("search_zip_code", {
      description: "Search zip code data",
      inputSchema: z.object({
        zipCode: z.string(),
      }),
    }, async (args) => {
      const result = await searchZipCode(args.zipCode);
    
      if (!result.results || result.results.length === 0) {
        return {
          content: [
            {
              type: "text",
              text: "No results found",
            },
          ],
        };
      }
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result),
          },
        ],
      };
    });
  • Input schema for 'search_zip_code' using Zod: expects a single 'zipCode' string parameter.
    inputSchema: z.object({
      zipCode: z.string(),
    }),
  • Core handler logic: searchZipCode async function that fetches from the zipcloud API endpoint with the given zipCode and returns parsed JSON.
    const SEARCH_ENDPOINT = "https://zipcloud.ibsnet.co.jp/api/search";
    
    const searchZipCode = async (zipCode: string) => {
        const response = await fetch(`${SEARCH_ENDPOINT}?zipcode=${zipCode}`);
        const data = await response.json();
        return data;
    };
    
    export { searchZipCode };
Behavior2/5

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

No annotations are provided, so the description carries full burden for disclosing behavior. It only says 'Search' without indicating whether it is read-only, requires authentication, or what the response looks like. Significant behavioral gaps exist.

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

Conciseness3/5

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

The description is extremely concise (4 words), which is efficient but arguably under-specified. It is front-loaded but lacks structure or additional details that could be provided without harming conciseness. Balanced between brevity and completeness.

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 tool's simplicity (one parameter, no output schema, no annotations), the description is incomplete. It does not explain what kind of data is returned, error conditions, or any usage notes. The agent is left with many unknowns.

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 0% schema description coverage, the parameter 'zipCode' lacks documentation in the schema. The description adds minimal value by implying the input is the search term, but it does not specify format, country, or constraints. Some meaning is added beyond the raw schema.

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 states 'Search zip code data', which clearly indicates the verb (search) and the resource (zip code data). It is specific enough to convey the tool's primary function, though slightly vague as 'zip code data' could be more precise. With no sibling tools, differentiation is not needed.

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, nor any context about prerequisite conditions, input formats, or use cases. The agent receives no help in deciding if this tool is appropriate.

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/tanish-kr/mcp-server-zipcode-jp'

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