Skip to main content
Glama
0xKoller

MCP Argentina Datos

by 0xKoller

dolares-historico

Access historical exchange rates for multiple Argentine currency exchange houses to track past dollar valuations.

Instructions

Devuelve las cotizaciones de todas las casas de cambio.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.ts:214-248 (handler)
    The handler function for the 'dolares-historico' tool, registered via server.tool. It invokes getDolaresHistorico, handles empty results and errors, and returns the data as formatted JSON.
    server.tool(
      "dolares-historico",
      "Devuelve las cotizaciones de todas las casas de cambio.",
      {},
      async ({}) => {
        try {
          const data = await getDolaresHistorico();
          if (data.length === 0) {
            return {
              content: [
                { type: "text", text: "No se encontraron cotizaciones de dólares" },
              ],
            };
          }
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(data, null, 2),
                mimeType: "application/json",
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: "Error al obtener las cotizaciones de dólares",
              },
            ],
          };
        }
      }
    );
  • main.ts:42-46 (schema)
    Static input schema definition for the 'dolares-historico' tool in the MCP server initialization (no parameters required).
    {
      name: "dolares-historico",
      description: "Devuelve las cotizaciones de todas las casas de cambio.",
      parameters: {},
    },
  • Helper function that fetches historical dollar exchange rates from the Argentina Datos API endpoint.
    export const getDolaresHistorico = async () => {
      const dolares = await fetch(`${BASE_URL}/cotizaciones/dolares/`);
      const data = await dolares.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 exchange rates but does not specify behavioral traits like data freshness, rate limits, error handling, or authentication needs. For a tool with zero annotation coverage, this is a significant gap, as it leaves the agent guessing about operational details. The description does not contradict any annotations, but it lacks essential context.

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 cotizaciones de todas las casas de cambio.' It is front-loaded with the core purpose, has zero waste, and is appropriately sized for a tool with no parameters. Every word earns its place, making it highly concise and well-structured.

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

Completeness3/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, no parameters) and lack of annotations or output schema, the description is minimally complete. It states what the tool does but does not provide enough context for effective use, such as output format, data scope (e.g., historical vs. current), or error handling. With no output schema, the description should ideally explain return values, but it does not. This makes it adequate but with clear gaps, scoring a 3.

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 schema description coverage is 100%, so there are no parameters to document. The description does not need to add parameter semantics beyond the schema. According to the rules, 0 parameters baseline is 4, as the description appropriately focuses on the tool's purpose without unnecessary parameter details.

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 'Devuelve las cotizaciones de todas las casas de cambio' clearly states the tool's purpose: returning exchange rates from all exchange houses. It uses a specific verb ('devuelve') and resource ('cotizaciones'), but does not explicitly distinguish it from sibling tools like 'dolares-por-casa' or 'dolares-por-casa-fecha', which likely provide more specific data. This clarity earns a 4, as it's understandable but lacks sibling 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 does not mention any context, prerequisites, or exclusions, such as comparing it to sibling tools like 'dolares-por-casa' for per-house data or specifying if it returns historical or current rates. Without such information, the score is 2, as there is minimal implicit usage context.

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