Skip to main content
Glama
Sign In
bluebonnet-sales

bluebonnet-sales

by hostedinthebarn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_order_status

Idempotent

Change an order's status; preview first, then set confirm=True to apply. Delivered or cancelled orders are final and cannot be changed.

Instructions

Change an order's status. Without confirm=True this only previews the change.

Delivered and cancelled orders are final and can't be changed.

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": {
      "order_id": "<order_id>",
      "status": "<status>"
    },
    "name": "update_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
confirmNo
order_idYes

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?

Annotations declare readOnlyHint=false and idempotentHint=true, and the description adds the dry-run default implied by confirm=false plus the terminal-state restriction on delivered/cancelled orders. That is genuine behavioral context beyond structured fields, though it does not say whether a preview returns a diff or what a rejected status change looks like.

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?

Two short sentences, front-loaded with the action and immediately followed by the safety-relevant confirm semantics and the state restriction. No filler.

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 3-parameter mutation tool with annotations covering the safety profile and no output schema, the definition covers the critical flow (preview then apply) and the hard constraint (final states). The remaining gap is the valid status vocabulary.

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 0%, so the description must carry parameter meaning. It explains confirm (preview vs apply) well, but says nothing about which status values are accepted for the required status parameter or the order_id format — the single most important invocation risk is left undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Change an order's status'), which is unambiguous action language. The sibling tools are all read/query tools (list_tables, run_query, sales_summary), so this is clearly the only mutating tool in the set, though the description does not explicitly say so.

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?

Gives concrete invocation guidance: without confirm=True it only previews, so the agent knows the two-step flow. It also states an exclusion — delivered and cancelled orders can't be changed — which is real when-not-to-use guidance. No named alternatives, but none exist among the siblings.

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

Deploy Server

Other Tools