Skip to main content
Glama
tremendous-mcp

tremendous-mcp

by Bryan21B

List orders

list_orders
Read-only

Retrieve orders newest first and filter by creation date range, campaign, external ID, or status to locate pending approvals and monitor order activity.

Instructions

List orders, newest first. Filter by creation date range, campaign, external_id, or status (for example PENDING APPROVAL to find orders that wait for approval).

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": "list_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNoISO 8601 date or datetime, inclusive
untilNoISO 8601 date or datetime, inclusive
offsetNo
statusNoFiltered after fetching: the API has no status filter, so up to `limit` orders are scanned.
campaign_idNo
external_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this a read-only, open-world operation, so the safety profile is covered. The description adds the "newest first" ordering, which is useful. However, it actively promotes filtering by status without disclosing the significant caveat captured in the schema that status is filtered after fetching and only up to `limit` orders are scanned — a material accuracy risk for an agent relying on the status filter.

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 sentences, zero filler, with the ordering behavior front-loaded before the filter inventory. Every clause carries an actual filter or behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With seven optional parameters and no output schema, the description covers most of the calling surface, but it omits pagination expectations (default limit, offset) and the post-fetch status scan caveat. For a read-only listing tool this is adequate, but an agent could over-trust the status filter.

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?

Schema description coverage is only 43%, so the description must compensate, and it does: it maps creation date range to since/until, names campaign and external_id, and supplies a concrete status value. Only limit and offset go unmentioned, and those are self-explanatory with schema defaults.

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 opens with a specific verb and resource ("List orders") plus a default ordering ("newest first"), and enumerates the filter dimensions. It is clearly distinguishable from get_order by the plural listing framing, though it never names that sibling explicitly.

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?

It gives concrete usage contexts for each filter, including a worked example ("PENDING APPROVAL to find orders that wait for approval"), which tells an agent when a given filter is the right lever. It stops short of explicit when-not guidance or pointing to alternatives such as get_order for a single record.

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