Skip to main content
Glama

Pay2GPT

Business: list orders

list_business_orders
Read-onlyIdempotent

For a company with a Pay2GPT business API key: its latest orders, newest first, each with its order number, product, status, redemption link and timestamps. Optionally only orders in one status.

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_business_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many orders, 1-50, default 20
statusNoOnly orders in this status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds genuinely new behavior: results are newest-first and each record carries a fixed set of fields including a redemption link. It does not say what 'latest' means in practice or that the default cap is 20, leaving the agent to discover the schema default on its own.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact fragments with the audience/auth scope front-loaded and the optional filter last; every clause carries information. The noun-phrase style ('its latest orders, newest first, each with...') is dense but readable, and there is no filler or repetition.

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 two-parameter read tool with no output schema, the description compensates well by enumerating the returned fields and their ordering. It does not address truncation behavior when more orders exist than the limit allows, which is the one thing an agent would still have to learn by calling it.

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%, so both parameters are already fully documented, including the 1-50 range and default 20 for limit and the status enum. The description only echoes the status filter ('optionally only orders in one status') and adds nothing about the limit parameter. Baseline 3 is appropriate when the schema does the work.

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 ('list... latest orders') plus the exact payload the agent gets back: order number, product, status, redemption link, timestamps. That is far more than a restatement of the name. It stops short of naming sibling tools like get_business_order or cancel_business_order, so the agent must infer that this is the collection-level read rather than a single-order fetch.

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?

The opening clause sets a clear precondition: this is for a company holding a Pay2GPT business API key, which tells the agent when the tool is applicable. The status filter is framed as optional, so the agent knows the unfiltered call is valid. There is no explicit when-not guidance or pointer to get_business_order for a single order.

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