Skip to main content
Glama
0xKoller

MCP Argentina Datos

by 0xKoller

eventos-presidenciales

Access presidential events data from Argentina to track official activities and engagements through the Argentina Datos API.

Instructions

Devuelve los eventos presidenciales

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.ts:187-211 (handler)
    Handler function registered with MCP server for the 'eventos-presidenciales' tool. It calls getEventosPresidenciales() and formats the response as JSON or handles errors.
    server.tool(
      "eventos-presidenciales",
      "Devuelve los eventos presidenciales",
      {},
      async ({}) => {
        try {
          const data = await getEventosPresidenciales();
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(data, null, 2),
                mimeType: "application/json",
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              { type: "text", text: "Error al obtener los eventos presidenciales" },
            ],
          };
        }
      }
    );
  • Helper function that performs the actual API fetch for presidential events from https://api.argentinadatos.com/v1/eventos/presidenciales/
    export const getEventosPresidenciales = async () => {
      const eventos = await fetch(`${BASE_URL}/eventos/presidenciales/`);
      const data = await eventos.json();
      return data;
    };
  • main.ts:37-41 (schema)
    Tool schema definition in the MCP server's tools list for discovery, specifying name, description, and empty parameters.
    {
      name: "eventos-presidenciales",
      description: "Devuelve los eventos presidenciales",
      parameters: {},
    },
  • main.ts:187-211 (registration)
    Registration of the 'eventos-presidenciales' tool with the MCP server using server.tool(), including schema and handler.
    server.tool(
      "eventos-presidenciales",
      "Devuelve los eventos presidenciales",
      {},
      async ({}) => {
        try {
          const data = await getEventosPresidenciales();
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(data, null, 2),
                mimeType: "application/json",
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              { type: "text", text: "Error al obtener los eventos presidenciales" },
            ],
          };
        }
      }
    );
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 events, implying a read-only operation, but does not specify aspects like data format, rate limits, authentication needs, or whether it's a query or static list. This lack of detail makes it insufficient for understanding the tool's behavior beyond a basic action.

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, clear sentence in Spanish: 'Devuelve los eventos presidenciales'. It is front-loaded with the core action and resource, with no unnecessary words or structural fluff. This makes it highly concise and efficiently structured.

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 complexity (simple read operation with no parameters) and the absence of annotations and output schema, the description is incomplete. It fails to explain what 'eventos presidenciales' includes (e.g., types of events, date ranges, or return format), leaving gaps in understanding the tool's full context and output.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description does not add parameter details, which is appropriate since there are none to describe. This aligns with the baseline score of 4 for tools with zero parameters, as no additional semantic information is needed.

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

Purpose2/5

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

The description 'Devuelve los eventos presidenciales' (Returns presidential events) is a tautology that essentially restates the tool name 'eventos-presidenciales' in Spanish. It specifies a verb ('devuelve') and resource ('eventos presidenciales'), but lacks detail about what these events entail or how they differ from other political tools like 'diputados' or 'senadores'. This makes it vague and minimally informative.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention context, prerequisites, or exclusions, and fails to differentiate it from sibling tools such as 'get-feriados' or 'diputados-actas'. This absence of usage instructions leaves the agent without direction for selection.

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