Skip to main content
Glama
luizzzvictor

mcp-comexstat

by luizzzvictor

getHarmonizedSystem

Search and retrieve harmonized system codes for trade classification. Specify language, page, and results per page to streamline trade data navigation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addNo
languageNopt
pageNo
perPageNo

Implementation Reference

  • MCP tool handler function for getHarmonizedSystem that receives parameters, calls the ComexstatClient.getHarmonizedSystem method, stringifies the result, and returns it as text content.
    async ({ language, page, perPage, add }) => ({
      content: [
        {
          type: "text",
          text: JSON.stringify(
            await this.client.getHarmonizedSystem({
              language,
              page,
              perPage,
              add,
            })
          ),
        },
      ],
    })
  • Zod input schema defining optional parameters: language (default 'pt'), page (default 1), perPage (default 10), and add.
    {
      language: z.string().optional().default("pt"),
      page: z.number().optional().default(1),
      perPage: z.number().optional().default(10),
      add: z.string().optional(),
    },
  • Registration of the 'getHarmonizedSystem' tool on the MCP server, specifying name, input schema, and handler function.
    this.server.tool(
      "getHarmonizedSystem",
      {
        language: z.string().optional().default("pt"),
        page: z.number().optional().default(1),
        perPage: z.number().optional().default(10),
        add: z.string().optional(),
      },
      async ({ language, page, perPage, add }) => ({
        content: [
          {
            type: "text",
            text: JSON.stringify(
              await this.client.getHarmonizedSystem({
                language,
                page,
                perPage,
                add,
              })
            ),
          },
        ],
      })
    );
  • Supporting client method that performs the actual API GET request to '/tables/hs' endpoint with provided options and returns the Harmonized System classification data.
    async getHarmonizedSystem(options?: {
      language?: string;
      page?: number;
      perPage?: number;
      add?: string;
    }): Promise<{
      data: {
        list: Array<{
          noNCM: string; // NCM description
          unit: string; // Measurement unit
          subHeadingCode: string; // HS subheading code
          subHeading: string; // HS subheading description
          headingCode: string; // HS heading code
          heading: string; // HS heading description
          chapterCode: string; // HS chapter code
          chapter: string; // HS chapter description
          coNcm: string; // NCM code
        }>;
        count: number; // Total number of records
      };
      success: boolean;
      message: string | null;
      processo_info: any;
      language: string;
    }> {
      return this.get("/tables/hs", options);
    }
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