Skip to main content
Glama

actualizar_estado

Updates an order's status through valid transitions (pendiente → preparando → enviado → entregado) or cancels it only from pendiente/preparando; owner access required.

Instructions

Avanza el estado de un pedido. Solo el dueño del negocio puede usarla. Las transiciones válidas son pendiente → preparando → enviado → entregado; cancelar solo desde pendiente o preparando.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "numero": "<numero>",
      "estado": "<estado>"
    },
    "name": "actualizar_estado"
  }
}

Input Schema

NameRequiredDescriptionDefault
notaNoComentario para el historial (máximo 500 caracteres).
estadoYesEstado nuevo.
numeroYesNúmero de pedido, por ejemplo "P-0002".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the key behavioral traits: an owner-only permission gate and a strict state machine with reversal limits. It does not say what happens when an invalid transition is requested (error vs. no-op), whether the call is idempotent, or what the response contains after a successful advance.

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?

Three short sentences with zero filler: purpose first, permission second, transition rules last. The ordering puts the action ahead of the constraints, so the agent gets the gist on the first line.

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 three-parameter mutation tool with no annotations and no output schema, the definition covers the two hardest things an agent needs: authorization and legal transitions. The remaining gap is failure and return behavior after a successful call, which matters somewhat for a mutation but is not blocking.

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 description coverage is 100%, so the baseline is 3; the description earns an extra point because it constrains the 'estado' enum with ordering semantics that the schema alone does not express. The 'nota' and 'numero' parameters are fully covered by the schema and need no further narrative.

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 states a specific verb and resource ("Avanza el estado de un pedido") and immediately distinguishes itself from the read/create siblings by being the state-transition operation. An agent can tell this is neither a query nor a creation tool without opening any schema.

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?

It gives a hard authorization precondition ("Solo el dueño del negocio puede usarla") and explicit when-not rules via the valid transition chain and the restriction on cancelling only from pendiente or preparando. It stops short of naming an alternative tool for cases that fall outside the chain, so the agent must infer that consultar_pedido is the way to inspect state.

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