Skip to main content
Glama
MSPbotsAI

pax8-mcp

by MSPbotsAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pax8_list_invoice_items

Retrieve line items for a specific invoice using its ID. Supports pagination with page and size parameters to control the result set.

Instructions

List line items for a specific invoice.

    Args:
        invoice_id: The unique identifier of the invoice.
        page: Zero-based page number for pagination (default: 0).
        size: Number of results per page (default: 10).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sizeNo
invoice_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the operation and parameters, without mentioning error conditions, auth requirements, rate limits, or side effects. It does not contradict any annotations, but adds minimal behavioral context beyond the obvious list action.

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, with the purpose front-loaded and each sentence earning its place. It avoids unnecessary verbosity and clearly lists parameters in a structured format.

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 tool has an output schema, so return values are covered there. The description explains pagination semantics and the required invoice_id. For a simple list tool, it provides all essential information an agent needs to call it correctly. Minor gaps like error handling are not critical for this complexity level.

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 0%, so the description must compensate. It does: each parameter gets a brief explanation, including that page is zero-based and size is per-page count. This adds meaning beyond the bare schema fields, though not deeply.

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 action (list), resource (line items), and scope (specific invoice). This distinguishes it from sibling tools like pax8_list_invoices or pax8_list_subscriptions, which target different resources.

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 usage context is implied: use this tool when you need line items for a specific invoice. However, there is no explicit guidance on when not to use it or how it compares to alternatives such as pax8_list_invoices or pax8_list_usage_summary_lines.

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