Cuéntica MCP

Overview Schema Source Related Servers Discussions Admin

list_invoices

Read-only

Retrieve invoices with filters for status, dates, customer, and amount. Enable summary to return only ID, number, date, customer, total, status, and paid.

Instructions

Lista facturas. issued=True emitidas, False borradores. sort ej: 'date:desc'. Fechas yyyy-MM-dd. Para borradores (issued=False) sin fechas especificadas se aplica automáticamente el año en curso. summary=True devuelve solo id, number, date, customer, total, status, paid (menos tokens).

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

Input Schema

Name	Required	Description	Default
`issued`	No
`initial_date`	No
`end_date`	No
`customer`	No
`description`	No
`serie`	No
`tags`	No
`min_total_limit`	No
`max_total_limit`	No
`sort`	No
`page`	No
`page_size`	No
`summary`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0May 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Adds behavioral context beyond annotations: automatic current year for drafts without specified dates, sort example, and summary functionality reducing tokens. Annotations already declare readOnlyHint=true, so the description supplements with specific query behaviors.

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?

The description is relatively concise, conveying key points in a few sentences. It could benefit from better structuring (e.g., bullet points), but it is not verbose and front-loads essential information.

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?

Given 13 parameters and an output schema, the description covers core filtering (issued, dates, sort, summary) but omits many filters and pagination details. The output schema exists, so return values are documented, leaving moderate gaps in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates by explaining issued, dates, sort, and summary parameters. However, many parameters (customer, description, serie, tags, min_total_limit, max_total_limit, page, page_size) are not described, leaving significant gaps.

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?

Clearly states it lists invoices, distinguishes between issued and drafts, and mentions summary mode. The verb 'Lista' and resource 'facturas' are specific, and the description differentiates it from siblings like list_expenses or list_income.

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?

Provides guidance on using the issued parameter to toggle between issued and drafts, mentions automatic year for drafts without dates, and explains the summary parameter for reduced tokens. However, it does not explicitly state when to use this tool versus other list tools, but the context is clear.

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

Deploy Server