Skip to main content
Glama

update_order_settings

Modify order settings: set prefixes and suffixes, add or remove ignored phones/emails, and manage helper shortcuts for automated responses.

Instructions

Configurar pedidos — Configura prefijos de pedidos y telefonos/emails a ignorar [mutation]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_prefixNoPrefijo para numeros de pedido (ej: #, PED-)#
order_suffixNoSufijo para numeros de pedido
add_ignore_phoneNoTelefono a ANADIR sin borrar los existentes. USAR SIEMPRE ESTE para anadir telefonos.
remove_ignore_phoneNoTelefono a eliminar de la lista de ignorados
add_ignore_emailNoEmail a ANADIR sin borrar los existentes. USAR SIEMPRE ESTE para anadir emails.
remove_ignore_emailNoEmail a eliminar de la lista de ignorados
add_helperNoJSON para crear o actualizar un atajo. Formato: {"name": "NOMBRE_CORTO", "text": "TEXTO_DEL_ATAJO", "send": true/false}. El campo 'send' activa el envio automatico (el atajo se envia al cliente sin que el agente pulse enviar). Si no se incluye 'send', se desactiva por defecto. Ejemplo con envio automatico: {"name": "compra VIN ok", "text": "la compra esta correcta para dicho numero de bastidor", "send": true}. Si ya existe un atajo con el mismo nombre, se actualiza (util para activar/desactivar envio automatico sin recrear el atajo).
remove_helperNoNombre corto del atajo a eliminar (ej: bastidor)
ignore_phonesNoLista de telefonos a ignorar (JSON array)
ignore_emailsNoLista de emails a ignorar (JSON array)
helpersNoLista de helpers (JSON array)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only notes [mutation] but lacks details on reversibility, permissions, or side effects. Minimal behavioral disclosure.

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?

Extremely concise: one line front-loads the purpose, with no wasted words. Despite being in Spanish, it is efficient and clear.

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

Completeness2/5

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

Given 11 parameters, no output schema, and no annotations, the description is too sparse. It does not explain behavior like append vs replace, or what the tool returns after mutation.

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% with detailed descriptions, so baseline is 3. The description adds high-level grouping but no new meaning 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 clearly states it configures order prefixes and phones/emails to ignore, with a [mutation] tag indicating modification. This distinguishes it from siblings like update_agent or update_campaign.

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?

No explicit guidance on when to use this tool versus alternatives. It only implies context for order settings, but does not provide when-not or alternative tool references.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wazionapps/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server