Datos UY/AR

Convertir UVA a pesos argentinos

ar_uva_convertir

Convierte un monto entre UVA y pesos argentinos al valor de la UVA de una fecha (default hoy).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "monto": "<monto>"
    },
    "name": "ar_uva_convertir"
  }
}

Input Schema

Name	Required	Default
`de`	No	UVA
`fecha`	No
`monto`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 9, 2026

TDQS

C2.9/5.0

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, and it only discloses the date default. It says nothing about which UVA source/rate is used, rounding or precision of the result, behavior on non-business days, or error cases, all of which matter for a currency-conversion tool.

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?

A single front-loaded sentence with no filler; the core action comes first and the date default is parenthetically attached. Somewhat terse for the gaps it must cover, but nothing is wasted.

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?

For a simple conversion tool with no annotations, no output schema, and 0% parameter coverage, the description covers purpose and date-default behavior but omits rate source, precision, and output shape. Adequate but with clear gaps given the absence of any structured support.

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?

Schema description coverage is 0%, so the description must compensate and it only partly does: it references 'monto', the directional 'entre UVA y pesos', and notably the 'fecha (default hoy)' behavior, which the schema does not state. It never explains the 'de' enum parameter's direction semantics (default UVA meaning UVA→ARS), leaving that to inference.

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?

States a specific verb ('convierte') and resource ('un monto entre UVA y pesos argentinos'), making the conversion intent unambiguous. It doesn't name or contrast with the sibling ar_uva (which presumably returns the raw UVA value), so it stops one step short of full 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?

There is no explicit when-to-use guidance, no mention of prerequisites, and no routing advice versus ar_uva or the ARS-side siblings. Usage is only inferable from the verb 'convierte'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Datos UY/AR tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?