Skip to main content
Glama

My orders

my_orders
Read-onlyIdempotent

Your own Barmaan orders, newest first: number, status, payment status, total, currency, date, item count. Filter by status (new, confirmed, shipped, delivered, cancelled, open, all), paid (paid/unpaid) or q (order number or item name). Also returns counts and your unpaid totals. Page with next_cursor.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "my_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOrder number or item name.
paidNo
limitNo
cursorNoValue of next_cursor from the previous page.
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: fixed newest-first ordering, inclusion of aggregate counts and unpaid totals, and cursor-based paging. It omits rate limits or auth notes, but nothing contradicts the annotations.

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?

Front-loaded with purpose and return shape, then filters, then extras, then pagination, in compact clause form with no filler. Every clause carries information an agent would otherwise have to guess.

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?

There is no output schema, so listing the returned fields and the extra counts/unpaid totals is necessary and done well. The only real gap is the undocumented limit bound, which matters for paging but is minor against the otherwise complete picture.

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?

With only 40% schema coverage, the description compensates by naming the allowed status values, the paid/unpaid split, what q matches (order number or item name), and how cursor paging works via next_cursor. Only the limit parameter's range and default (1-20, default 10) are left undocumented in both places.

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+resource ('Your own Barmaan orders') and enumerates the returned fields (number, status, payment status, total, currency, date, item count). The scope word 'own' plus the plural resource clearly separates it from the singular sibling get_my_order.

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?

Filtering behavior is spelled out (status, paid, q) and pagination is mentioned, which implies when the tool is appropriate, but there is no explicit statement of when to prefer this over get_my_order or track_my_order and no exclusions.

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.

Resources