Skip to main content
Glama
luizzzvictor

mcp-comexstat

by luizzzvictor

getAvailableYears

Retrieve available years of data accessible through the mcp-comexstat server, enabling users to identify and select specific timeframes for analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registers the MCP tool 'getAvailableYears' with empty input schema. The handler fetches available years via the client and returns a JSON string in text content.
    this.server.tool("getAvailableYears", {}, async () => ({
      content: [
        {
          type: "text",
          text: JSON.stringify(await this.client.getAvailableYears()),
        },
      ],
    }));
  • Inline handler function for the 'getAvailableYears' tool that calls the client method and formats the response as JSON text.
    this.server.tool("getAvailableYears", {}, async () => ({
      content: [
        {
          type: "text",
          text: JSON.stringify(await this.client.getAvailableYears()),
        },
      ],
    }));
  • Implements the getAvailableYears logic by calling the Comexstat API GET /general/dates/years endpoint and extracting the {min, max} data.
    async getAvailableYears(): Promise<{ min: string; max: string }> {
      const response = await this.get<{
        data: { min: string; max: string };
        success: boolean;
        message: string | null;
        processo_info: any;
        language: string;
      }>("/general/dates/years");
      return response.data;
    }
  • TypeScript type definitions for input/output of getAvailableYears: returns Promise<{ min: string; max: string }> and expects API response with data: { min: string; max: string }.
    async getAvailableYears(): Promise<{ min: string; max: string }> {
      const response = await this.get<{
        data: { min: string; max: string };
        success: boolean;
        message: string | null;
        processo_info: any;
        language: string;
      }>("/general/dates/years");
      return response.data;
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