Skip to main content
Glama
MSPbotsAI

pax8-mcp

by MSPbotsAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pax8_list_invoices

Retrieve invoices from your Pax8 partner account. Filter by company, status, and sort by date to manage billing records.

Instructions

List invoices 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. "invoiceDate,desc".
        company_id: Filter by company ID.
        status: Filter by invoice status, e.g. "Paid", "Unpaid", "Overdue".

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

A4.1/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It accurately describes a read-only listing operation but does not explicitly mention side effects, error behavior, or pagination limits beyond the parameter defaults.

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 concise and well-structured, with a short opening line followed by bullet-like parameter explanations. No unnecessary information is included.

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?

The description provides enough contextual detail for an agent to invoke the tool correctly, including parameter semantics and defaults. Since an output schema is available, not describing the return structure is acceptable, though a brief note on expected errors or authorization could make it slightly more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All five parameters are described clearly, including defaults, the zero-based page index, and examples for sort and status filters. This fully compensates for the 0% schema description coverage.

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?

The description clearly states the tool's purpose: listing invoices in the Pax8 partner account. It provides a specific verb and resource, distinguishing it from related tools like invoice items.

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 description explains the parameters and gives examples, but it does not explicitly state when to use this tool versus sibling tools such as pax8_list_invoice_items. The intended usage is implied by the name and parameters, but not explicitly contrasted with alternatives.

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