Skip to main content
Glama

conduyt_list_invoices

Retrieve invoices filtered by status, contact, or date range to locate specific billing records.

Instructions

List invoices with filtering by status, contact, or date range.

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": "conduyt_list_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1)
statusNoFilter by status (e.g. 'draft', 'sent', 'paid', 'overdue', 'voided')
date_toNoEnd of date range (ISO 8601)
per_pageNoResults per page
date_fromNoStart of date range (ISO 8601)
contact_idNoFilter by contact UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.71.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must carry the whole behavioral burden. It never states that this is a read-only operation, how pagination defaults/l limits behave (page vs per_page), or whether results are sorted or capped — all material for a paginated list tool.

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?

A single, front-loaded sentence with no wasted words. Brevity is a virtue here, though the space saved is not used for anything more useful.

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?

Parameters are fully covered by the schema and there is no output schema, so the description needn't explain return values. However, for a paginated list tool with zero annotations, the absence of any mention of result shape, paging defaults, or read-only safety leaves a real gap.

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 all six parameters are already documented, and the description only restates the filter dimensions (status, contact, date range) without adding format or combination semantics. Baseline 3 applies when the schema does the heavy lifting.

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?

Specific verb+resource ("List invoices") plus the filtering dimensions, which lets an agent distinguish it from conduyt_get_invoice and the create/update/send invoice siblings. It does not explicitly name those siblings, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to use this versus conduyt_get_invoice (single record) or conduyt_search. The listing intent is only implied by the verb "List", and nothing covers prerequisites or result-size expectations.

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