Skip to main content
Glama
0xKoller

MCP Argentina Datos

by 0xKoller

dolares-por-casa-fecha

Get the exchange rate for a specific currency house in Argentina on a given date. Input the house name and date in YYYY/MM/DD format to retrieve the dollar value.

Instructions

Devuelve la cotización del dólar de la casa de cambio especificada en la fecha indicada (en formato YYYY/MM/DD).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
casaYesEJ: blue, oficial, cripto, etc.
fechaYesEJ: 2025/01/01

Implementation Reference

  • main.ts:316-368 (handler)
    MCP tool handler for 'dolares-por-casa-fecha': validates casa and fecha parameters, calls getDolaresPorCasaFecha helper, handles empty results and errors, returns JSON or text response.
    async ({ casa, fecha }) => {
      if (!casa) {
        return {
          content: [
            {
              type: "text",
              text: "No se ha provisto el parámetro 'casa'",
            },
          ],
        };
      }
      if (!fecha) {
        return {
          content: [
            {
              type: "text",
              text: "No se ha provisto el parámetro 'fecha'",
            },
          ],
        };
      }
      try {
        const data = await getDolaresPorCasaFecha(casa, fecha);
        if (data.length === 0) {
          return {
            content: [
              {
                type: "text",
                text: "No se encontraron cotizaciones de dólares para la casa de cambio especificada en la fecha indicada",
              },
            ],
          };
        }
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(data, null, 2),
              mimeType: "application/json",
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: "Error al obtener la cotización del dólar para la casa de cambio especificada en la fecha indicada",
            },
          ],
        };
      }
    }
  • Core helper function implementing the tool logic: fetches dollar quotation data for specified casa and fecha from the Argentina Datos API.
    export const getDolaresPorCasaFecha = async (casa: string, fecha: string) => {
      const dolares = await fetch(
        `${BASE_URL}/cotizaciones/dolares/${casa}/${fecha}`
      );
      const data = await dolares.json();
      return data;
    };
  • Zod input schema for tool parameters: 'casa' (string, e.g., blue), 'fecha' (string matching YYYY/MM/DD regex).
    {
      casa: z.string().describe("EJ: blue, oficial, cripto, etc."),
      fecha: z
        .string()
        .regex(
          /^\d{4}\/(0[1-9]|1[0-2])\/(0[1-9]|[12][0-9]|3[01])$/,
          "El formato de la fecha debe ser YYYY/MM/DD"
        )
        .describe("EJ: 2025/01/01"),
    },
  • main.ts:303-369 (registration)
    Full registration of the 'dolares-por-casa-fecha' tool with MCP server, specifying name, description, schema, and handler function.
    server.tool(
      "dolares-por-casa-fecha",
      "Devuelve la cotización del dólar de la casa de cambio especificada en la fecha indicada (en formato YYYY/MM/DD).",
      {
        casa: z.string().describe("EJ: blue, oficial, cripto, etc."),
        fecha: z
          .string()
          .regex(
            /^\d{4}\/(0[1-9]|1[0-2])\/(0[1-9]|[12][0-9]|3[01])$/,
            "El formato de la fecha debe ser YYYY/MM/DD"
          )
          .describe("EJ: 2025/01/01"),
      },
      async ({ casa, fecha }) => {
        if (!casa) {
          return {
            content: [
              {
                type: "text",
                text: "No se ha provisto el parámetro 'casa'",
              },
            ],
          };
        }
        if (!fecha) {
          return {
            content: [
              {
                type: "text",
                text: "No se ha provisto el parámetro 'fecha'",
              },
            ],
          };
        }
        try {
          const data = await getDolaresPorCasaFecha(casa, fecha);
          if (data.length === 0) {
            return {
              content: [
                {
                  type: "text",
                  text: "No se encontraron cotizaciones de dólares para la casa de cambio especificada en la fecha indicada",
                },
              ],
            };
          }
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(data, null, 2),
                mimeType: "application/json",
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: "Error al obtener la cotización del dólar para la casa de cambio especificada en la fecha indicada",
              },
            ],
          };
        }
      }
    );
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a read operation ('devuelve' - returns) but doesn't mention potential limitations like rate limits, authentication requirements, error conditions, or what happens with invalid dates/houses. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 perfectly concise - a single sentence that efficiently communicates the core functionality and includes the date format specification. Every word earns its place with zero waste or redundancy.

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 moderate complexity (2 required parameters, no output schema, no annotations), the description is minimally adequate but incomplete. It covers the basic purpose and parameter format but lacks guidance on usage context, behavioral constraints, and output expectations. The absence of annotations and output schema means the description should do more to compensate.

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 schema description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds minimal value beyond the schema by specifying the date format (YYYY/MM/DD) and implying this is for exchange rate queries, but doesn't provide additional context about parameter semantics or usage examples.

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 tool's purpose: 'Devuelve la cotización del dólar de la casa de cambio especificada en la fecha indicada' (Returns the dollar exchange rate of the specified exchange house on the indicated date). It uses specific verbs ('devuelve' - returns) and resources ('cotización del dólar' - dollar exchange rate), though it doesn't explicitly differentiate from sibling tools like 'dolares-historico' or 'dolares-por-casa'.

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 sibling tools like 'dolares-historico' or 'dolares-por-casa', nor does it specify any prerequisites, exclusions, or contextual constraints beyond the basic parameter requirements.

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