Project Tango

Simulate Order Placement

simulate_order_placement

Place a simulated order by validating stock for each item, decrementing inventory, and computing the total from current prices; reject the whole order if any item is unavailable.

Instructions

Write-action tool: places a new simulated order, validating stock availability for every line item, decrementing inventory counts, computing the order total from current catalog prices, and returning a success receipt with the updated stock levels. Rejects the entire order (no partial writes) if any item is unavailable or under-stocked. The whole read-validate-write runs inside the provider's transaction, so a concurrent order cannot both pass a stock check and oversell. This permanently changes the dataset until reset_demo_state is called.

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

Input Schema

Name	Required	Description	Default
`items`	Yes	One or more line items for this order.
`customer_name`	Yes	Full name of the customer placing the order.

Output Schema

Name	Required	Description	Default
`receipt`	Yes
`success`	Yes
`updatedStockLevels`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.0Nov 10, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly: all-or-nothing writes ('no partial writes'), transactional isolation against concurrent oversell, and permanent dataset mutation until reset_demo_state is called. These are exactly the mutation semantics an agent must know before invoking.

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 dense sentences, front-loaded with the write-action framing, with zero filler. Each sentence adds a distinct fact: what it does, atomicity, and transaction/persistence behavior.

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?

An output schema exists, so the description needn't detail return values, yet it still previews the 'success receipt with updated stock levels'. Combined with the atomicity and persistence notes, an agent has everything needed to call this safely.

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 customer_name, items, product_id, and quantity are already documented in the schema. The description adds behavioral meaning (per-line-item stock validation, totals from current catalog prices) but no syntax or constraint detail beyond the schema, matching the baseline 3.

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?

Opens with an explicit verb+resource ('places a new simulated order') and enumerates the concrete operations performed (stock validation, inventory decrement, total computation). It also distinguishes itself from siblings by naming reset_demo_state as the inverse operation.

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?

Frames the tool as a 'Write-action tool' and states the persistence consequence plus the reset_demo_state escape hatch, which tells an agent when this is appropriate versus read-only siblings. It stops short of explicitly contrasting against alternatives like find_orders or list_all_products, so a 4 rather than 5.

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

Deploy Server