mueblito

Search furniture by name

buscar_catalogo

Read-only

Busca por NOMBRE entre los muebles armables de Mueblito (los mismos que listar_presets), con stemming en español. Todo lo que devuelve es un mueble fabricable a medida (melamina/MDF) con un link al editor 3D (editor_url). Usala cuando el usuario describe lo que busca ('cama', 'silla comedor', 'placard') para encontrar el/los id y después construir_mueble (recomendado) con ese id. (search parametric furniture presets by name, find buildable furniture Argentina, cut list)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`consulta`	Yes	Texto libre en español para buscar en el catálogo. Ejemplos: 'cama', 'silla comedor', 'banqueta de barra'. Soporta variantes morfológicas (plural/singular, acentos). Máximo 200 caracteres.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`resultados`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 15, 2026
- addedOutput schema / properties / resultados / items / properties / ambiente
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / resultados / items / properties / editor_url
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / resultados / items / properties / imagen_url
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / resultados / items / properties / precio_ars
```
Removed value: -{
-  "type": "number"
-}
```
- changedOutput schema / properties / resultados / items / required
```
Previous value: -[
-  "id",
-  "nombre",
-  "categoria",
-  "medidas_mm",
-  "nota"
-]New value: +[
+  "id",
+  "nombre",
+  "categoria",
+  "medidas_mm",
+  "nota",
+  "ambiente",
+  "editor_url",
+  "imagen_url"
+]
```
First observedSep 1, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already provide readOnlyHint=true and openWorldHint=false. The description adds concrete behavioral context: Spanish stemming, results are buildable custom melamine/MDF furniture, and each result includes an editor_url. This is valuable beyond the annotations and does not contradict them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core information is front-loaded and readable, with purpose, output, and usage clearly stated. However, the trailing parenthetical with English keywords and 'cut list' is low-value clutter that does not earn its place in the description.

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 single-parameter, read-only, schema-rich search tool, the description covers scope, matching behavior, result type, and the recommended downstream tool. The only notable gap is the absence of guidance on result ordering, limits, or behavior when no matches are found.

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 coverage is 100%, and the schema's 'consulta' description already documents free Spanish text, examples, morphological variants, and max length. The description adds 'stemming' and focuses on name search, but these are largely redundant with the schema, providing only marginal extra meaning.

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 verb ('Busca por NOMBRE') and resource ('muebles armables de Mueblito'), and clarifies it operates on the same catalog as listar_presets. It also describes the returned item type and editor_url, making the tool's purpose unambiguous.

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?

Explicitly tells the agent when to use the tool: when the user describes a piece of furniture such as 'cama' or 'silla comedor', and to then pass the resulting id to construir_mueble. It does not include explicit when-not-to-use exclusions or alternative selection conditions beyond mentioning the sibling catalog.

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

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?