Paidnice

List actions

list_actions

Read-onlyIdempotent

Returns what Paidnice has scheduled, sent, skipped or failed (reminders, late fees, statements, SMS, escalations and so on), newest first, up to 100 per page. Each action has its status, run dates, any notes or error, and the policies that created it. Filter by contact, invoice, status or type. Read only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organisationId": "<organisationId>"
    },
    "name": "list_actions"
  }
}

Input Schema

Name	Required	Description
`type`	No	Only actions of this type, for example reminder, late_fee or send_statement
`limit`	No	Maximum number of records to return
`cursor`	No	Opaque cursor from a previous response's nextCursor. Omit to start from the most recent record.
`status`	No	pending: waiting for its run date. complete: done. failed: errored, see errorMessage. suspended and approval_pending: waiting for a user. skipped: skipped by a user. reverted: a late fee that was later reversed.
`contactId`	No	Only actions for this contact
`invoiceId`	No	Only actions for this invoice, including statements and statement late fees that included it
`organisationId`	Yes	Id of the organisation to act on, from list_organisations

Output Schema

Name	Required	Description	Default
`data`	Yes
`nextCursor`	No	Pass as the cursor query parameter to fetch the next page. Absent on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: newest-first ordering, a 100-per-page cap, and the shape of each returned action (status, run dates, notes/error, originating policies). The closing 'Read only.' merely restates the annotation and earns nothing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense, front-loaded sentences: what it returns, what each record contains, how to filter. Almost every clause carries information, with the sole waste being 'Read only.', which duplicates the readOnlyHint annotation.

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

Completeness5/5

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

With an output schema present, the description need not document return values, and it still outlines ordering, page size and record contents. Filters, scoping and read-only behavior are all covered, so an agent has everything needed to call this correctly.

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 100%, so the schema already explains every parameter, including the enum semantics for status and type. The description adds only a summary of the four filter axes and an implicit reference to pagination via 'up to 100 per page'; it says nothing extra about limit or cursor beyond the schema. Baseline 3 applies.

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 names a specific resource (scheduled/sent/skipped/failed actions) and enumerates the concrete action categories (reminders, late fees, statements, SMS, escalations), plus ordering and page size. It does not explicitly differentiate itself from siblings like list_notes or list_invoices, though the resource name makes the distinction reasonably inferable.

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 states the available filter axes (contact, invoice, status, type), which implies how the tool is meant to be narrowed, but gives no explicit when-to-use guidance, no when-not guidance, and never routes the agent to a sibling such as get_invoice or check_contact_policies for a single-record or policy view.

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

All Paidnice tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?