Skip to main content
Glama

Virág — Manhattan flower delivery

Get order status

get_order_status

Status of an order: awaiting_payment, paid, placed (sent to florist), delivered, expired, refunded.

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>"
    },
    "name": "get_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYesThe order_id returned by create_order (starts with vg_)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real value by enumerating the complete status vocabulary, including the clarifying gloss 'placed (sent to florist)', which tells the agent what a return value means. However, it says nothing about read-only semantics, what happens for an unknown or malformed order_id, or whether the status reflects live florist state.

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?

One compact sentence with the status list front-loaded and zero filler. The parenthetical gloss on 'placed' is the only elaboration and it earns its place.

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 one-parameter read tool with no output schema, disclosing the full status vocabulary effectively covers the return value, which is the main thing an agent needs. The remaining gap is error behavior for invalid or missing order IDs, which the absence of an output schema leaves entirely undocumented.

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% and the single order_id parameter is already documented with its origin (returned by create_order) and prefix format (vg_). The description adds no further meaning about the parameter, so the baseline of 3 applies.

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?

The description names the resource (an order) and the exact attribute returned (status), so an agent can distinguish it from create_order or list_bouquets. It stops short of a verb phrasing or any explicit contrast with the closest sibling, check_delivery, leaving the status-vs-delivery boundary to inference.

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?

There is no when-to-use or when-not-to-use guidance at all. Nothing tells the agent whether this is the right call after create_order versus check_delivery, or whether it applies to orders in any state including expired and refunded.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.