Skip to main content
Glama
gabrielnika

Elorus MCP Server

by gabrielnika

list_invoices

List sales invoices with filters for date range, status, payment, client, and search terms. Get a summary of matching invoices to easily locate specific ones.

Instructions

List sales invoices with summary fields; use get_invoice for full details.

Filters:

  • period_from / period_to: issue-date range, YYYY-MM-DD; only applied when BOTH are given.

  • status: one of draft, pending, issued, partial, unpaid, overdue, paid, void.

  • paid: True = fully paid invoices only, False = not fully paid.

  • overdue: True = overdue invoices only.

  • draft: True = drafts only, False = finalized only.

  • client: Elorus contact ID of the client (find it with list_contacts).

  • search: free-text search term (number, client name, etc.).

  • ordering: comma-separated sort fields, prefix with '-' for descending, e.g. '-date' or 'client__display_name'. Returns {count, page, results}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
paidNo
draftNo
clientNo
searchNo
statusNo
overdueNo
orderingNo
page_sizeNo
period_toNo
period_fromNo
Behavior5/5

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

With no annotations, the description carries the full burden. It discloses filter behavior (e.g., period range only applied when both are given), the boolean semantics, and the return shape {count, page, results}, making the tool's behavior transparent.

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 well-structured with a one-line overview followed by a neatly formatted filter list. Every sentence provides essential information and no redundancy, making it highly efficient.

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?

Given 11 parameters, no annotations, and no output schema, the description thoroughly documents all key filters, return format, and pagination-related behavior. It covers all necessary aspects for correct invocation.

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?

Schema coverage is 0%, so the description must compensate. It explains the meaning of all filter parameters including status values, boolean logic for paid/draft/overdue, the client ID lookup, and ordering syntax. This exceeds the schema's bare names and types.

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 tool lists sales invoices with summary fields, and explicitly distinguishes itself from get_invoice for full details. This makes the purpose specific and differentiates it from the sibling.

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

Usage Guidelines5/5

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

The description explicitly says to use get_invoice for full details, providing a clear alternative. It also elaborates on filter semantics, giving the agent context on when to apply each parameter.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gabrielnika/Elorus-ERP-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server