Skip to main content
Glama
xiaobenyang-com

Philippine-Geocoding

get_region_municipalities

get_region_municipalities

Retrieve a list of municipalities for any Philippine region using its region code to access geographic data.

Instructions

Get all municipalities within a specific region

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionCodeYes

Implementation Reference

  • Core handler logic that executes the tool by proxying the request to the remote API endpoint 'https://mcp.xiaobenyang.com/api' using the tool name 'get_region_municipalities' and arguments. This is the implementation shared by all dynamic tools.
    const calcXiaoBenYangApi = async function (fullArgs: Record<string, any>) {
        // 发起 POST 请求
        let response = await fetch('https://mcp.xiaobenyang.com/api', {
            method: 'POST',
            headers: {
                'XBY-APIKEY': apiKey,
                'func': fullArgs.toolName,
                'mcpid': mcpID
            },
            body: new URLSearchParams(fullArgs)
        });
        const apiResult = await response.text();
    
        return {
            content: [
                {
                    type: "text",
                    text: apiResult // 将字符串结果放入 content 中
                }
            ]
        } as { [x: string]: unknown; content: [{ type: "text"; text: string }] };
    };
  • Wrapper handler that validates and prepares arguments by adding the toolName 'get_region_municipalities', then calls the core API proxy.
    const handleXiaoBenYangApi = async (args: Record<string, any>, toolName: string) => {
        // 校验aid是否存在
        if (toolName === undefined || toolName === null) {
            throw new Error("缺少必要参数 'aid'");
        }
        // 合并参数
        const fullArgs = {...args, toolName: toolName};
        // 调用API
        return calcXiaoBenYangApi(fullArgs);
    };
  • src/mcp.ts:50-65 (registration)
    Registration helper that calls server.registerTool for a given tool name (e.g., 'get_region_municipalities'), description, and schema, using the generic handler.
    const addToolXiaoBenYangApi = function (
        name: string,
        desc: string,
        params: Record<string, ZodType>
    ) {
        server.registerTool(
            name,
            {
                title: name,
                description: desc,
                inputSchema: params,
            }
            ,
            async (args: Record<string, any>) => handleXiaoBenYangApi(args, name)
        )
    };
  • src/mcp.ts:89-132 (registration)
    Dynamic tool registration loop: fetches tool list from remote API (https://mcp.xiaobenyang.com/getMcpDesc?mcpId=1777316659371011), parses schemas, and registers all tools including 'get_region_municipalities'.
    for (const apiDesc of apiDescList) {
        let inputSchema = JSON.parse(apiDesc.inputSchema);
        const zodDict: Record<string, z.ZodTypeAny> = {};
    
        Object.entries(inputSchema.properties).forEach(([name, propConfig]) => {
            let zodType;
            let pt = (propConfig as { type: string }).type;
            switch (pt) {
                case 'string':
                    zodType = z.string();
                    break;
                case 'number':
                    zodType = z.number();
                    break;
                case 'boolean':
                    zodType = z.boolean();
                    break;
                case 'integer':
                    zodType = z.int32();
                    break;
                case 'array':
                    zodType = z.array(z.any());
                    break;
                case 'object':
                    zodType = z.object(z.any());
                    break;
                default:
                    zodType = z.any();
            }
    
            if (inputSchema.required?.includes(name)) {
                zodDict[name] = zodType;
            } else {
                zodDict[name] = zodType.optional();
            }
        });
    
    
        addToolXiaoBenYangApi(
            apiDesc.name,
            apiDesc.description ? apiDesc.description : apiDesc.name,
            zodDict);
    }
  • Dynamic input schema construction using Zod based on JSON schema from remote tool description for 'get_region_municipalities'.
    Object.entries(inputSchema.properties).forEach(([name, propConfig]) => {
        let zodType;
        let pt = (propConfig as { type: string }).type;
        switch (pt) {
            case 'string':
                zodType = z.string();
                break;
            case 'number':
                zodType = z.number();
                break;
            case 'boolean':
                zodType = z.boolean();
                break;
            case 'integer':
                zodType = z.int32();
                break;
            case 'array':
                zodType = z.array(z.any());
                break;
            case 'object':
                zodType = z.object(z.any());
                break;
            default:
                zodType = z.any();
        }
    
        if (inputSchema.required?.includes(name)) {
            zodDict[name] = zodType;
        } else {
            zodDict[name] = zodType.optional();
        }
    });
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. It states the action ('Get') but doesn't describe whether this is a read-only operation, what format the output takes (list of names, objects with details), potential errors (invalid region codes), or performance characteristics (e.g., pagination). The description is minimal and leaves critical behavioral aspects unspecified.

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, clear sentence that states exactly what the tool does without unnecessary words. It's front-loaded with the core functionality ('Get all municipalities within a specific region') and contains no redundant information. Every word earns its place in this efficiently structured 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?

Given the complexity (1 required parameter, no output schema, no annotations), the description is incomplete. It doesn't explain what a 'region' is in this context, what data is returned about municipalities, or how to handle potential issues like invalid region codes. For a tool with zero schema description coverage and no output schema, the description should provide more context about both inputs and expected outputs.

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

Parameters2/5

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

Schema description coverage is 0%, so the schema provides no parameter documentation. The description mentions 'within a specific region' which implies the 'regionCode' parameter is required, but doesn't explain what constitutes a valid region code (format, examples, or where to find valid codes). Given the low coverage, the description fails to adequately compensate for the schema's lack of parameter documentation.

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 verb ('Get') and resource ('all municipalities within a specific region'), making the purpose immediately understandable. It distinguishes itself from siblings like 'get_municipalities' (which presumably gets all municipalities without regional filtering) and 'get_region' (which gets region details rather than its municipalities). However, it doesn't explicitly contrast with all relevant siblings like 'get_region_cities_municipalities' which might return both cities and municipalities.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing a valid region code), exclusions (e.g., whether it returns only municipalities or includes cities), or direct comparisons to siblings like 'get_region_cities_municipalities' or 'get_municipalities'. The agent must infer usage from the name and description 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/xiaobenyang-com/Philippine-Geocoding'

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