Skip to main content
Glama

Pay2GPT

Business: get an order

get_business_order
Read-onlyIdempotent

For a company with a Pay2GPT business API key: one of its orders by order number, with its current status.

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_number": "<order_number>"
    },
    "name": "get_business_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_numberYesThe order number

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?

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description usefully adds the auth scope (business API key required) and hints that the response carries the order's current status, but says nothing about not-found/error behavior or freshness of the status.

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?

One compact sentence with the key gating condition (business API key) placed first, followed by the operation. The phrasing 'one of its orders' is slightly elliptical but wastes no words.

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?

For a one-parameter read tool this is close to sufficient, and it does hint at the returned status field. With no output schema, a bit more on what 'current status' contains (and on missing-order behavior) would be needed for full completeness.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines 'order_number'. The description only restates that the lookup is by order number, adding no format or validation details beyond the schema.

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 ('one of its orders by order number') plus the scope constraint ('For a company with a Pay2GPT business API key'). Singular-order retrieval is implicitly distinguished from the sibling list_business_orders, though no sibling is named.

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?

The prerequisite is explicit: the caller must be a company holding a Pay2GPT business API key. It does not say when to prefer this over list_business_orders, nor what to do if the order number is unknown — usage is only implied.

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