Skip to main content
Glama
MSPbotsAI

pax8-mcp

by MSPbotsAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pax8_list_products

List products available in the Pax8 marketplace with support for pagination, sorting, and filtering by vendor or product name.

Instructions

List products available in the Pax8 marketplace.

    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. "productName,asc".
        vendor_name: Filter by vendor name (partial match).
        product_name: Filter by product name (partial match).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sizeNo
sortNo
vendor_nameNo
product_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The description uses 'List', which implies a read-only operation, and provides parameter descriptions that clarify behavior. With no annotations provided, the description alone conveys the non-destructive nature, though it does not explicitly state side-effect-free or idempotent behavior.

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 brief and to the point, containing only the action, resource, and a compact parameter list. There is no redundant or filler text.

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 context for a straightforward list operation, including parameter semantics and an example for sort. It does not describe the return format, but for a simple listing tool the output is likely self-explanatory, and the presence of an output schema mitigates this gap.

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?

Each of the five parameters is described in the Args section with clear semantics: page (zero-based), size (results per page), sort (field and direction with example), vendor_name (partial match filter), and product_name (partial match filter). This fully covers the schema parameters and adds meaning beyond their titles and defaults.

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 products') and the target resource ('Pax8 marketplace'), distinguishing it from sibling tools that list other entities like companies, invoices, or subscriptions.

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 description indicates it is a listing operation with optional filters and pagination parameters. It does not explicitly contrast with alternative tools, but the resource name 'products' is sufficiently specific to avoid ambiguity with siblings.

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