Skip to main content
Glama
0xKoller

MCP Argentina Datos

by 0xKoller

dolares-por-casa

Get current exchange rates for specific dollar types in Argentina, including blue, official, and crypto rates, to monitor currency values.

Instructions

Devuelve las cotizaciones del dólar de la casa de cambio especificada.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
casaYesEJ: blue, oficial, cripto, etc.

Implementation Reference

  • main.ts:251-300 (handler)
    MCP tool handler for 'dolares-por-casa': validates 'casa' input, fetches data using getDolaresPorCasa, handles errors, and returns JSON response.
    server.tool(
      "dolares-por-casa",
      "Devuelve las cotizaciones del dólar de la casa de cambio especificada.",
      {
        casa: z.string().describe("EJ: blue, oficial, cripto, etc."),
      },
      async ({ casa }) => {
        if (!casa) {
          return {
            content: [
              {
                type: "text",
                text: "No se ha provisto el parámetro 'casa'",
              },
            ],
          };
        }
        try {
          const data = await getDolaresPorCasa(casa);
          if (data.length === 0) {
            return {
              content: [
                {
                  type: "text",
                  text: "No se encontraron cotizaciones de dólares para la casa de cambio especificada",
                },
              ],
            };
          }
          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 para la casa de cambio especificada",
              },
            ],
          };
        }
      }
    );
  • Core helper function that fetches dollar exchange rates for the specified 'casa' from the Argentina Datos API.
    export const getDolaresPorCasa = async (casa: string) => {
      const dolares = await fetch(`${BASE_URL}/cotizaciones/dolares/${casa}`);
      const data = await dolares.json();
      return data;
    };
  • main.ts:47-54 (schema)
    Input schema definition for 'dolares-por-casa' tool in the McpServer tools list.
    {
      name: "dolares-por-casa",
      description:
        "Devuelve las cotizaciones del dólar de la casa de cambio especificada.",
      parameters: {
        casa: z.string().describe("EJ: blue, oficial, cripto, etc."),
      },
    },
  • main.ts:251-300 (registration)
    Registration of the 'dolares-por-casa' tool via server.tool, including schema and handler.
    server.tool(
      "dolares-por-casa",
      "Devuelve las cotizaciones del dólar de la casa de cambio especificada.",
      {
        casa: z.string().describe("EJ: blue, oficial, cripto, etc."),
      },
      async ({ casa }) => {
        if (!casa) {
          return {
            content: [
              {
                type: "text",
                text: "No se ha provisto el parámetro 'casa'",
              },
            ],
          };
        }
        try {
          const data = await getDolaresPorCasa(casa);
          if (data.length === 0) {
            return {
              content: [
                {
                  type: "text",
                  text: "No se encontraron cotizaciones de dólares para la casa de cambio especificada",
                },
              ],
            };
          }
          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 para la casa de cambio especificada",
              },
            ],
          };
        }
      }
    );
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 doesn't describe the return format (e.g., JSON structure, units), potential errors (e.g., invalid 'casa' values), rate limits, or authentication needs. For a data-fetching tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 that efficiently conveys the tool's purpose without unnecessary words. It's front-loaded with the core function and appropriately sized for a simple tool with one parameter. Every part of the sentence earns its place by specifying what is returned and for what resource.

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 low complexity (one parameter, no nested objects, no output schema) and 100% schema coverage, the description is minimally adequate. However, without annotations or an output schema, it lacks details on return values, error handling, and behavioral context. For a data retrieval tool, this leaves room for improvement in completeness, but it's not critically incomplete.

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%, with the single parameter 'casa' documented as 'EJ: blue, oficial, cripto, etc.' The description adds no additional parameter semantics beyond what the schema provides. Since the schema fully covers the parameter, the baseline score of 3 is appropriate, as the description doesn't need to compensate but also doesn't add extra value.

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 las cotizaciones del dólar de la casa de cambio especificada' (Returns the dollar exchange rates for the specified exchange house). It specifies the verb ('devuelve' - returns) and resource ('cotizaciones del dólar' - dollar exchange rates), making the function unambiguous. However, it doesn't differentiate from sibling tools like 'dolares-historico' or 'dolares-por-casa-fecha', which likely serve related purposes.

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' (likely for historical data) or 'dolares-por-casa-fecha' (likely for date-specific queries), nor does it specify prerequisites, exclusions, or appropriate contexts. The user must infer usage from the tool name and description alone.

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