Skip to main content
Glama
Sign In

Cambio Uruguay

by io.github.eduair94
OverviewDiscussionsAdmin

Cuánto sale equipar una casa

plan_home_setup
Read-onlyIdempotent

Presupuesto para equipar una vivienda vacía (ideal después de alquilar sin amueblar): canasta mínima, decente o completa, línea por línea con precio y si conviene usado o nuevo, restando lo que la persona ya tiene. Si faltan precios de algún ítem el total es parcial y lo dice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "plan_home_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
haveNoLo que ya tiene: "heladera", "colchón", "microondas"…
levelNominima (lo imprescindible, default), decente, completa.
conditionNocheapest (default: usado cuando conviene) o new (todo nuevo).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, open-world, idempotent, non-destructive behavior, and the description adds meaningful output behavior beyond that: line-by-line pricing, used-vs-new recommendations, subtraction of items already owned, and explicit partial totals when prices are missing.

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?

Two tightly written sentences front-load the purpose and follow with scope and output caveats. The parenthetical context is useful and no sentence is wasted.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the output explanation itself: line items, pricing, used/new advice, subtraction of owned items, and partial totals. Combined with fully described optional parameters and safety annotations, an agent has enough information to invoke it correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantic value by explaining that 'have' is subtracted from the budget and that the condition choice affects whether used or new is recommended per line item. It does not add formatting or default details beyond what the schema already provides.

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 and resource: producing a budget to equip an empty home, scoped to unfurnished-rental scenarios. The purpose is clear and distinct from property-search siblings, but it does not explicitly differentiate itself from named alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear usage context ('ideal después de alquilar sin amueblar') and explains the basket levels and used/new choice. It stops short of naming when not to use it or pointing to an alternative sibling.

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

All Cambio Uruguay toolsInspect
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