alga-psa-mcp

Official

Overview Schema Source Related Servers Discussions Admin

alga_invoices_list

Read-only

List invoices page by page and filter by client, status, invoice date range, or due date range to retrieve matching billing records.

Instructions

List invoices, one page at a time. Filter by client, status, invoice date range or due date range (YYYY-MM-DD, inclusive).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "alga_invoices_list"
  }
}

Input Schema

Name	Required	Description
`page`	No
`sort`	No
`limit`	No
`order`	No
`status`	No
`client_id`	No
`due_date_to`	No	Date as YYYY-MM-DD.
`due_date_from`	No	Date as YYYY-MM-DD.
`invoice_date_to`	No	Date as YYYY-MM-DD.
`invoice_date_from`	No	Date as YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The readOnlyHint and destructiveHint annotations already establish that this is a safe read. The description adds useful behavior beyond that: results are paginated and date ranges are inclusive. It omits return shape, whether a total count is returned, default ordering, and whether unfiltered calls scan the whole account.

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?

Two short sentences, front-loaded with the core action and pagination caveat, then the filter dimensions. No redundant restatement of the name and no filler.

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 10-parameter list tool with no output schema and only read-only annotations, the description covers filtering and pagination adequately but leaves sorting, page/limit tuning defaults, and result metadata unexplained. It is minimum viable rather than complete.

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?

Schema description coverage is only 40% across 10 parameters, so the description carries real weight; it clarifies that date filters are inclusive and formatted YYYY-MM-DD, and that status and client are filters. It says nothing about sort, order, page, or limit semantics, leaving roughly half the parameters explained only by schema types and defaults.

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 states a specific verb and resource ("List invoices") and adds the two defining traits: pagination and filterability. It is distinguishable from alga_invoices_get and alga_invoices_items_list by naming invoices as paged records rather than a single record or line items, though it does not explicitly contrast with them.

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?

It implies usage (browse invoices, narrow by client/status/date) and notes results come one page at a time, so an agent knows to page. It gives no explicit when-to-use guidance, no pointer to alga_invoices_get for a single invoice, and no statement about what to do when no filters are supplied.

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

Deploy Server