Skip to main content
Glama

crear_pedido

Create a new pending order for the current session's customer. Use whole-cent integer prices and get back the created order with its order number.

Instructions

Crea un pedido nuevo en estado pendiente para el cliente de esta sesión. Los precios van en centavos enteros (precio_centavos), nunca con decimales. Devuelve el pedido creado con su número.

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": {
      "items": "<items>"
    },
    "name": "crear_pedido"
  }
}

Input Schema

NameRequiredDescriptionDefault
notaNoAclaración opcional (máximo 500 caracteres).
itemsYesÍtems del pedido (1 a 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description must carry the behavioral burden. It usefully discloses the initial state (pending), the integer-cents constraint, and the return value (the created order with its number). It omits authorization requirements, uniqueness/duplicate behavior, and rate/error conditions, so it is strong but not complete.

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 tightly packed sentences, front-loaded with the core action and state, then the critical price-format warning, then the return value. No filler or redundancy.

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 create tool with no annotations and no output schema, the description covers the essential points: initial state, price format, and the shape of the return value. Auth/permission expectations and validation failure behavior are the main omissions, keeping it below a 5.

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 description coverage is 100%, so the schema already documents both parameters, establishing the baseline of 3. The description's note that prices are integer cents reinforces a common error source but largely repeats the existing schema field for precio_centavos rather than adding new 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 and resource ("Crea un pedido nuevo") plus the initial state ("en estado pendiente") and scope ("para el cliente de esta sesión"). This makes it immediately distinguishable from read/update siblings like consultar_pedido, actualizar_estado or listar_pedidos.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: creating a new order versus the sibling read/list/update tools is fairly self-evident. However, the description gives no explicit when-to-use, no when-not-to-use, and no prerequisites (e.g., whether a client must exist first).

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