mueblito

cotizar_mueble

Read-only

Calcula el presupuesto de materiales en ARS para fabricar un mueble a medida: placas/melamina, tapacanto, herrajes y servicio de corte en maderera. Usala cuando el usuario quiere saber cuánto sale hacer un mueble en Argentina. Prerrequisito: si no sabés el id del preset, llamá primero a listar_presets; los ids disponibles son los que acepta este campo (ej: 'placard-corredizo', 'biblioteca', 'escritorio-cajonera'). Podés ajustar las medidas del preset con el campo 'ajustes' sin necesidad de pasar todos los params. Limitación: precios orientativos de MercadoLibre Argentina (ARS), sin mano de obra ni instalación; se actualizan periódicamente y pueden variar. (quote furniture cost, materials budget Argentina, cut list price ARS)

Input Schema

TableJSON Schema

Name	Required	Description
`params`	No	Params paramétricos completos del mueble (alternativa a 'preset'). Requerido si no se pasa 'preset'. Debe incluir al menos: kind, width (mm), height (mm), depth (mm).
`preset`	No	ID del preset de mueble a cotizar. Requerido si no se pasa 'params'. Ejemplos: 'placard-corredizo', 'biblioteca', 'escritorio-cajonera', 'comoda', 'bajo-mesada'. Usá listar_presets para ver todos los ids disponibles.
`ajustes`	No	Ajustes de medidas opcionales sobre el preset. Solo los campos que querés sobreescribir.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`nota`	Yes
`lineas`	Yes
`mueble`	Yes
`total_ars`	Yes
`medidas_mm`	Yes
`total_formateado`	Yes

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the readOnlyHint=true annotation, the description discloses useful behavioral context: prices are indicative ARS values from MercadoLibre, exclude labor and installation, and can vary over time. This helps the agent set expectations about estimate accuracy and scope.

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?

The description is front-loaded with purpose, then organized into usage, prerequisite, adjustment note, and limitation. The final English parenthetical is redundant, but the overall length is justified by the tool's complexity.

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

Completeness4/5

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

For a complex tool with nested schemas and an output schema, the description covers purpose, when to use it, prerequisite setup, preset adjustments, and pricing limitations. It does not explain the full custom 'params' path, but the schema already documents that exhaustively.

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 description adds practical parameter knowledge beyond the 100% schema coverage: example preset ids, the ability to adjust presets via 'ajustes', and the fact that partial overrides are allowed. It does not re-document the schema, but reinforces the preset-based workflow.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific action ('Calcula el presupuesto de materiales...') and resource ('mueble a medida') with clear scope (ARS, materials, cut service). It also ties the tool to the user's intent ('saber cuánto sale hacer un mueble'), which distinguishes it from siblings like ver_mueble, crear_diseno, or despiece.

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?

Provides an explicit when-to-use signal ('Usala cuando el usuario quiere saber cuánto sale hacer un mueble en Argentina') and a concrete prerequisite: call listar_presets first if the preset id is unknown. It does not enumerate when-not-to-use or name alternatives, but the context is clear and actionable.

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

All mueblito tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clearly distinct deliverable: search, list, quote, cut list, preview, validate, refine, and compose a 3D design. Even though several share the same preset/params inputs, their purposes and outputs do not overlap in a confusing way.

Naming Consistency4/5

Most tools follow a consistent Spanish verb_noun pattern: ajustar_mueble, buscar_catalogo, cotizar_mueble, crear_diseno, listar_presets, validar_factibilidad, ver_mueble. Despiece breaks the pattern as a noun-only name, which is a minor deviation.

Tool Count5/5

Eight tools is well-scoped for a parametric furniture server. Each tool covers a distinct part of the workflow—discovery, quotation, cut lists, preview, feasibility, iteration, and 3D scene creation—without unnecessary redundancy.

Completeness5/5

The tool set covers the full parametric furniture lifecycle: find/list presets, preview, validate, quote, generate cut lists, refine designs, and create shareable 3D layouts. There are no obvious dead ends or missing operations for the stated purpose.

Resources

Need Help?