Skip to main content
Glama
luizzzvictor

mcp-comexstat

by luizzzvictor

getNBM

Retrieve and filter NBM data by language, page, and search terms using the MCP server. Customize results with pagination and additional parameters for precise queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addNo
languageNopt
pageNo
perPageNo
searchNo

Implementation Reference

  • MCP tool handler for 'getNBM' that serializes the result from ComexstatClient.getNBM into JSON text content.
        content: [
          {
            type: "text",
            text: JSON.stringify(
              await this.client.getNBM({ language, page, perPage, add, search })
            ),
          },
        ],
      })
    );
  • Input schema (Zod) for the 'getNBM' tool defining optional parameters: language, page, perPage, add, search.
      language: z.string().optional().default("pt"),
      page: z.number().optional().default(1),
      perPage: z.number().optional().default(5),
      add: z.string().optional(),
      search: z.string().optional(),
    },
  • Registration of the 'getNBM' MCP tool on the McpServer instance.
      "getNBM",
      {
        language: z.string().optional().default("pt"),
        page: z.number().optional().default(1),
        perPage: z.number().optional().default(5),
        add: z.string().optional(),
        search: z.string().optional(),
      },
      async ({ language, page, perPage, add, search }) => ({
        content: [
          {
            type: "text",
            text: JSON.stringify(
              await this.client.getNBM({ language, page, perPage, add, search })
            ),
          },
        ],
      })
    );
  • ComexstatClient helper method that performs the actual HTTP GET request to the /tables/nbm endpoint to retrieve NBM data.
    async getNBM(options?: {
      language?: string;
      page?: number;
      perPage?: number;
      add?: string;
      search?: string;
    }): Promise<{
      data: {
        list: Array<{
          noNCM: string; // NCM description
          unit: string; // Measurement unit
          nbm: string; // NBM description
          coNbm: string; // NBM code
          coNcm: string; // NCM code
        }>;
        count: number; // Total number of records
      };
      success: boolean;
      message: string | null;
      processo_info: any;
      language: string;
    }> {
      return this.get("/tables/nbm", 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