Skip to main content
Glama

mueblito

by ar.mueblito
OverviewDiscussionsAdmin

List furniture presets

listar_presets
Read-only

Lista los presets de muebles armables de Mueblito: id, nombre, tipo, medidas en mm, descripción y un link al editor 3D (editor_url) para abrir cada uno en el sitio. Opcionalmente filtrá por 'ambiente' (Dormitorio/Living/Cocina y comedor/Baño/Oficina/Exterior) para descubrir qué hay por espacio. Llamala para encontrar el id de un mueble; después construilo con construir_mueble (recomendado) o cotizá/mostrá con ese id. (list furniture presets, parametric furniture types by room, Argentina cut list)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ambienteNoFiltro opcional por ambiente: Dormitorio, Living, Cocina y comedor, Baño, Oficina, Exterior u Otros.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
presetsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / ambiente
      Added value: +{
+  "description": "Filtro opcional por ambiente: Dormitorio, Living, Cocina y comedor, Baño, Oficina, Exterior u Otros.",
+  "type": "string"
+}
    • addedOutput schema / properties / presets / items / properties / ambiente
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / presets / items / properties / editor_url
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / presets / items / properties / imagen_url
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / presets / items / required
      Previous value: -[
-  "id",
-  "nombre",
-  "tipo",
-  "medidas_mm",
-  "descripcion"
-]New value: +[
+  "id",
+  "nombre",
+  "tipo",
+  "medidas_mm",
+  "descripcion",
+  "ambiente",
+  "editor_url",
+  "imagen_url"
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces a read-only catalog list with no hidden mutation. It adds behavioral detail beyond the annotations by specifying the returned fields and the optional ambiente filter, plus the editor_url side effect of opening the editor. No contradictions or missing side effects are evident.

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 main behavior, filter, and downstream usage are packed into three front-loaded sentences. The trailing English parenthetical is redundant with the title and adds little, preventing a top score.

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?

For a low-complexity read-only list tool with an output schema and one optional parameter, the description covers purpose, filter values, return contents, and the next-step workflow. Nothing an agent needs to call or consume the result is missing.

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 already documents the optional ambiente parameter and its allowed values. The description restates those values and explains why filtering is useful, but does not add materially new semantic information beyond the schema.

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?

The description names a specific verb and resource ('Lista los presets de muebles armables de Mueblito') and enumerates the returned fields (id, nombre, tipo, medidas, descripción, editor_url), so an agent knows exactly what the tool produces. It also frames the tool as the discovery step before sibling tools, distinguishing it from construction/quoting tools.

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?

The description states a concrete use case ('Llamala para encontrar el id de un mueble') and directs the agent to the relevant sibling tools afterward (construir_mueble, cotizar/mostrar). It does not explicitly contrast with buscar_catalogo or give a when-not condition, so it falls just short of full routing guidance.

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

All mueblito 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