Skip to main content
Glama
0xKoller

MCP Argentina Datos

by 0xKoller

senado-actas-por-anio

Retrieve Argentine Senate session records for a specific year to access legislative proceedings and official documentation.

Instructions

Devuelve las actas del senado de un año específico

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anioYesEJ: 2025

Implementation Reference

  • main.ts:74-80 (registration)
    Initial tool registration and schema definition in the McpServer constructor's tools array.
    {
      name: "senado-actas-por-anio",
      description: "Devuelve las actas del senado de un año específico",
      parameters: {
        anio: z.number().describe("EJ: 2025"),
      },
    },
  • main.ts:423-470 (handler)
    MCP tool handler registration: validates 'anio' parameter, fetches data using getSenadoActasPorAnio, handles errors and formats response as JSON.
    // senado-actas-por-anio
    server.tool(
      "senado-actas-por-anio",
      "Devuelve las actas del senado de un año específico",
      {
        anio: z.number().describe("EJ: 2025"),
      },
      async ({ anio }) => {
        if (anio === undefined) {
          return {
            content: [
              {
                type: "text",
                text: "No se ha provisto el parámetro 'anio'",
              },
            ],
          };
        }
        try {
          const data = await getSenadoActasPorAnio(anio);
          if (data.length === 0) {
            return {
              content: [
                {
                  type: "text",
                  text: "No se encontraron actas para el año especificado",
                },
              ],
            };
          }
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(data, null, 2),
                mimeType: "application/json",
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              { type: "text", text: "Error al obtener las actas del senado" },
            ],
          };
        }
      }
    );
  • Core implementation: fetches senate actas for a specific year from the Argentina Datos API.
    export const getSenadoActasPorAnio = async (anio: number) => {
      const actas = await fetch(`${BASE_URL}/senado/actas/${anio}`);
      const data = await actas.json();
      return data;
    };
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool returns data ('devuelve'), implying a read-only operation, but doesn't clarify aspects like rate limits, authentication needs, error handling, or response format. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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

Conciseness5/5

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

The description is a single, efficient sentence: 'Devuelve las actas del senado de un año específico'. It's front-loaded with the core purpose, has zero wasted words, and is appropriately sized for a simple tool. Every part of the sentence contributes to understanding the tool's function.

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

Completeness2/5

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

Given the tool's simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It lacks details on return values (e.g., format, structure), error cases, or behavioral traits. While concise, it doesn't provide enough context for an agent to fully understand how to use the tool effectively beyond the basic parameter.

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

Parameters3/5

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

The description adds minimal meaning beyond the input schema. It mentions 'un año específico' (a specific year), which aligns with the 'anio' parameter documented in the schema with 100% coverage. However, it doesn't provide additional context like valid year ranges or format details. With high schema coverage, the baseline is 3, as the description doesn't compensate with extra insights.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Devuelve las actas del senado de un año específico' (Returns the senate minutes for a specific year). It specifies the verb ('devuelve' - returns) and resource ('actas del senado' - senate minutes), making the function unambiguous. However, it doesn't explicitly distinguish from sibling tools like 'senado-actas' (which likely returns all minutes without year filtering), missing full differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'senado-actas' (which might return all minutes) or 'senadores' (which might return senator data), nor does it specify prerequisites or exclusions. Usage is implied only by the parameter 'anio', but no explicit context is given.

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

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/0xKoller/mcp-argentina-datos'

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