Skip to main content
Glama
0xKoller

MCP Argentina Datos

by 0xKoller

senadores

Retrieve current Argentine senators and their legislative data to analyze government representation or track political activity.

Instructions

Devuelve los senadores.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.ts:372-394 (handler)
    Handler implementation for the 'senadores' tool. Calls getSenadores helper, handles empty data and errors, returns JSON response.
    server.tool("senadores", "Devuelve los senadores.", {}, async ({}) => {
      try {
        const data = await getSenadores();
        if (data.length === 0) {
          return {
            content: [{ type: "text", text: "No se encontraron senadores" }],
          };
        }
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(data, null, 2),
              mimeType: "application/json",
            },
          ],
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: "Error al obtener los senadores" }],
        };
      }
    });
  • main.ts:64-68 (schema)
    Schema definition for the 'senadores' tool in the MCP server constructor's tools list, indicating no input parameters.
    {
      name: "senadores",
      description: "Devuelve los senadores.",
      parameters: {},
    },
  • main.ts:371-394 (registration)
    Registration of the 'senadores' tool using server.tool, including inline handler.
    // senadores
    server.tool("senadores", "Devuelve los senadores.", {}, async ({}) => {
      try {
        const data = await getSenadores();
        if (data.length === 0) {
          return {
            content: [{ type: "text", text: "No se encontraron senadores" }],
          };
        }
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(data, null, 2),
              mimeType: "application/json",
            },
          ],
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: "Error al obtener los senadores" }],
        };
      }
    });
  • Helper function that fetches senators data from the Argentina Datos API.
    export const getSenadores = async () => {
      const senadores = await fetch(`${BASE_URL}/senado/senadores`);
      const data = await senadores.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 only states that it returns senators, without mentioning any behavioral traits such as whether it's a read-only operation, if it requires authentication, rate limits, pagination, or what format the output takes. For a tool with no annotations, 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.

Conciseness4/5

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

The description is a single, straightforward sentence: 'Devuelve los senadores.' It's front-loaded and wastes no words, making it highly concise. However, it could be slightly improved by adding a bit more context without losing efficiency, but it's appropriately sized for its minimal content.

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 (0 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain what 'returns the senators' entails—e.g., is it a list, details, current data? With no output schema and no annotations, the description should provide more context about the return value and behavior to be fully helpful, but it falls short.

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 tool has 0 parameters, and the input schema has 100% description coverage (though empty). With no parameters, the description doesn't need to add parameter semantics. The baseline for 0 parameters is 4, as there's nothing to compensate for, and the description doesn't contradict or confuse the parameterless nature.

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

Purpose3/5

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

The description 'Devuelve los senadores' (Returns the senators) states a clear verb ('devuelve') and resource ('senadores'), making the basic purpose understandable. However, it lacks specificity about what exactly is returned (e.g., list of senators, their details, current vs historical) and doesn't distinguish from sibling tools like 'senado-actas' or 'senado-actas-por-anio' that also relate to the senate. This makes it vague rather than specific.

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. There are multiple sibling tools related to legislative data (e.g., 'diputados', 'senado-actas'), but the description doesn't indicate if this is for current senators, historical data, or how it differs from other tools. Without any context on usage scenarios or exclusions, it offers minimal practical help.

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