Skip to main content
Glama
MSPbotsAI

pax8-mcp

by MSPbotsAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pax8_list_orders

List Pax8 partner account orders with pagination, sorting, and filters by company or status to retrieve order data for AI-driven workflows.

Instructions

List orders in the Pax8 partner account.

    Args:
        page: Zero-based page number for pagination (default: 0).
        size: Number of results per page (default: 10).
        sort: Sort field and direction, e.g. "orderDate,desc".
        company_id: Filter by company ID.
        status: Filter by order status, e.g. "Pending", "Completed", "Cancelled".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sizeNo
sortNo
statusNo
company_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior1/5

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

No annotations are present, and the description does not disclose any behavioral details such as read-only nature, side effects, rate limits, authentication requirements, or error behavior. The description adds no transparency beyond the raw operation name.

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?

The description is extremely concise, containing only the essential purpose statement and parameter explanations. No redundant or irrelevant content is present.

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

Completeness2/5

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

The description lacks information about return format, pagination behavior beyond the parameter defaults, filtering semantics, ordering rules, or error conditions. Given that the schema covers only parameter shapes and no output schema is shown, the description leaves major functional gaps for an agent.

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?

The schema provides only parameter names and types with zero description coverage. The description adds some semantic context by providing examples (e.g., sort 'orderDate,desc', status values) and explaining defaults, but it does not fully specify valid values, formats, or relationships between parameters.

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 clearly states the action ('List') and the resource ('orders') within the Pax8 partner account. It does not explicitly differentiate from sibling list tools, but the resource is unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives like pax8_list_subscriptions or pax8_list_invoices. The description only lists parameters without explaining context or conditions for use.

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

Deploy Server

Other Tools