Skip to main content
Glama
0xKoller

MCP Argentina Datos

by 0xKoller

diputados-actas-por-anio

Retrieve official legislative records for Argentine deputies by specifying a year to access detailed session minutes and proceedings.

Instructions

Devuelve las actas de los diputados de un año específico

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anioYesEJ: 2025

Implementation Reference

  • main.ts:498-544 (handler)
    MCP server.tool registration and handler function for the 'diputados-actas-por-anio' tool. It validates the 'anio' parameter, calls the helper getDiputadosActasPorAnio, handles errors, and returns JSON response.
    server.tool(
      "diputados-actas-por-anio",
      "Devuelve las actas de los diputados 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 getDiputadosActasPorAnio(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 de los diputados" },
            ],
          };
        }
      }
    );
  • Helper function that performs the actual API fetch for diputados actas by year from argentinadatos.com API.
    export const getDiputadosActasPorAnio = async (anio: number) => {
      const actas = await fetch(`${BASE_URL}/diputados/actas/${anio}`);
      const data = await actas.json();
      return data;
    };
  • main.ts:87-93 (schema)
    Tool schema definition in the server capabilities list, including name, description, and input parameters schema.
    {
      name: "diputados-actas-por-anio",
      description: "Devuelve las actas de los diputados de un año específico",
      parameters: {
        anio: z.number().describe("EJ: 2025"),
      },
    },
  • main.ts:4-16 (registration)
    Import statement registering the helper function getDiputadosActasPorAnio from utils/functions.js into main.ts.
    import {
      getFeriados,
      getEventosPresidenciales,
      getDolaresHistorico,
      getDolaresPorCasa,
      getDolaresPorCasaFecha,
      getSenadores,
      getSenadoActas,
      getSenadoActasPorAnio,
      getDiputados,
      getDiputadosActas,
      getDiputadosActasPorAnio,
      getSalud,
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. While it correctly describes a read operation ('Devuelve' - returns), it doesn't mention any behavioral traits like pagination, rate limits, authentication requirements, error conditions, or what happens when no data exists for the specified year. For a tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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 that states the core functionality without unnecessary words. It's appropriately sized for a simple tool with one parameter and gets straight to the point. Every word contributes to understanding the tool's purpose.

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 lack of annotations and output schema, the description is insufficiently complete. It doesn't explain what the return value contains (e.g., list of minutes, their structure, or metadata), nor does it address potential edge cases or error scenarios. For a data retrieval tool with no structured output documentation, the description should provide more context about what to expect from the response.

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 value beyond the input schema, which already has 100% coverage. It mentions the year parameter ('de un año específico') but doesn't provide additional context about valid ranges, format expectations beyond the schema's example, or how the year parameter affects the returned data. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate with meaningful parameter 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 verb ('Devuelve' - returns) and resource ('actas de los diputados' - deputies' minutes), making the purpose understandable. It specifies the scope ('de un año específico' - for a specific year), which helps distinguish it from the sibling tool 'diputados-actas' that likely returns all minutes without year filtering. However, it doesn't explicitly differentiate from other sibling tools like 'senado-actas-por-anio' which serves a similar function for senators.

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 the sibling tool 'diputados-actas' (which likely returns all minutes without year filtering) or 'senado-actas-por-anio' (which serves senators instead of deputies). There's no indication of prerequisites, constraints, or typical use cases beyond the basic year parameter.

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