Skip to main content
Glama
luizzzvictor

mcp-comexstat

by luizzzvictor

getStateDetails

Retrieve detailed state information by providing a unique UF ID using the MCP server mcp-comexstat. Simplifies access to essential state data for analysis or integration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ufIdYes

Implementation Reference

  • The MCP tool handler function for getStateDetails, which receives ufId parameter, calls this.client.getStateDetails(ufId), stringifies the result as JSON, and returns it wrapped in MCP content format.
    async ({ ufId }) => ({
      content: [
        {
          type: "text",
          text: JSON.stringify(await this.client.getStateDetails(ufId)),
        },
      ],
    })
  • Registration of the getStateDetails MCP tool using this.server.tool, specifying the tool name, input schema, and handler function.
    this.server.tool(
      "getStateDetails",
      {
        ufId: z.string(),
      },
      async ({ ufId }) => ({
        content: [
          {
            type: "text",
            text: JSON.stringify(await this.client.getStateDetails(ufId)),
          },
        ],
      })
    );
  • Input schema definition for the getStateDetails tool using Zod (z.string() for ufId).
    {
      ufId: z.string(),
    },
  • Supporting client method that implements the core logic for fetching state details from the API endpoint `/tables/uf/${ufId}`, returning structured data including state code, abbreviation, name, and region.
    async getStateDetails(ufId: string): Promise<{
      data: {
        coUf: string; // State code
        sgUf: string; // State abbreviation
        noUf: string; // State name
        noRegiao: string; // Region name
      };
      success: boolean;
      message: string | null;
      processo_info: any;
      language: string;
    }> {
      return this.get(`/tables/uf/${ufId}`);
    }
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