Skip to main content
Glama
0xKoller

MCP Argentina Datos

by 0xKoller

diputados

Access legislative data on Argentine deputies through the Argentina Datos API. Retrieve information about national representatives to support research, analysis, and civic engagement.

Instructions

Devuelve los diputados.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.ts:473-495 (handler)
    Handler implementation for the 'diputados' tool: calls getDiputados(), handles empty data and errors, returns JSON response.
    server.tool("diputados", "Devuelve los diputados.", {}, async ({}) => {
      try {
        const data = await getDiputados();
        if (data.length === 0) {
          return {
            content: [{ type: "text", text: "No se encontraron diputados" }],
          };
        }
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(data, null, 2),
              mimeType: "application/json",
            },
          ],
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: "Error al obtener los diputados" }],
        };
      }
    });
  • main.ts:81-85 (schema)
    Schema definition for the 'diputados' tool in the MCP server tools list, specifying name, description, and empty parameters.
    {
      name: "diputados",
      description: "Devuelve los diputados.",
      parameters: {},
    },
  • Core helper function getDiputados that fetches the list of diputados from the Argentina Datos API.
    export const getDiputados = async () => {
      const diputados = await fetch(`${BASE_URL}/diputados/diputados`);
      const data = await diputados.json();
      return data;
    };
  • main.ts:472-495 (registration)
    Registration of the 'diputados' tool handler on the MCP server.
    // diputados
    server.tool("diputados", "Devuelve los diputados.", {}, async ({}) => {
      try {
        const data = await getDiputados();
        if (data.length === 0) {
          return {
            content: [{ type: "text", text: "No se encontraron diputados" }],
          };
        }
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(data, null, 2),
              mimeType: "application/json",
            },
          ],
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: "Error al obtener los diputados" }],
        };
      }
    });
Behavior1/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 what the tool does at a superficial level ('returns the deputies') without any information about permissions, rate limits, data format, pagination, or whether it's a read-only operation. This is inadequate for a tool with zero annotation coverage.

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 extremely concise—a single Spanish phrase—with no wasted words. It's front-loaded and gets straight to the point, though this brevity comes at the cost of completeness. For its length, every word earns its place in conveying the basic 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, no output schema, and the presence of sibling tools, the description is incomplete. It doesn't explain what 'diputados' entails (e.g., current legislators, historical data, or something else), how results are returned, or how it differs from related tools like 'diputados-actas'. This leaves significant gaps for an AI agent to understand and use the tool effectively.

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 schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics beyond what the schema provides. A baseline score of 4 is appropriate as the description doesn't contradict the empty parameter set and the schema fully covers the lack of parameters.

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 diputados' (Returns the deputies) is a tautology that essentially restates the tool name 'diputados' in Spanish. It doesn't specify what kind of deputies (e.g., legislative, political party, timeframe) or what operation is performed (list, search, filter). While it indicates a retrieval action, it lacks specificity about scope or resource type.

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. With sibling tools like 'diputados-actas' and 'diputados-actas-por-anio' that appear related, there's no indication of how this tool differs (e.g., whether it returns current deputies, all historical deputies, or basic information vs. detailed records). No context or exclusions are mentioned.

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