Skip to main content
Glama
luizzzvictor

mcp-comexstat

by luizzzvictor

getCountries

Retrieve country data by entering a search query. Integrate with mcp-comexstat to access accurate and structured information for various applications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNo

Implementation Reference

  • Registration of the MCP tool 'getCountries'. Includes input schema (optional 'search' string validated by Zod) and the handler function that calls ComexstatClient.getCountries(search) and returns the result as JSON-formatted text content.
    this.server.tool(
      "getCountries",
      {
        search: z.string().optional(),
      },
      async ({ search }) => ({
        content: [
          {
            type: "text",
            text: JSON.stringify(await this.client.getCountries(search)),
          },
        ],
      })
    );
  • The core handler function in ComexstatClient that implements the logic for retrieving countries list from the API endpoint '/tables/countries', with optional search parameter. Includes JSDoc documentation and TypeScript type definitions for input/output.
    /**
     * Gets list of countries
     * @param search Optional search term to filter countries
     * @returns Array of countries with their codes and names
     */
    async getCountries(search?: string): Promise<{
      data: {
        list: Array<{
          id: string;
          text: string;
        }>;
      };
    }> {
      return this.get("/tables/countries", search ? { search } : undefined);
    }
  • Instantiation of the ComexstatClient instance used by the MCP server tools, including getCountries.
    this.client = new ComexstatClient();
  • Import of ComexstatClient module, resolving to the file containing the getCountries implementation.
    import ComexstatClient from "./ComexstatClient";
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

Related 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/luizzzvictor/mcp-comexstat'

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