Frihet MCP Server

List Quotes

list_quotes

Read-onlyIdempotent

List all quotes or estimates with filters by status, date range, client, or series. Supports pagination and field selection for targeted results.

Instructions

List all quotes/estimates with optional pagination and filters. Quotes are proposals sent to clients before they become invoices. Supports filtering by status (draft/sent/accepted/rejected/expired) and date range. Example: status='sent', from='2026-01-01', limit=20 / Lista todos los presupuestos con paginacion y filtros opcionales. Soporta filtrado por estado y rango de fechas.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	End date filter (YYYY-MM-DD) / Fecha fin
`from`	No	Start date filter (YYYY-MM-DD) / Fecha inicio
`after`	No	Cursor for cursor-based pagination (document ID) / Cursor para paginacion basada en cursor
`limit`	No	Max results (1-100) / Resultados maximos
`fields`	No	Comma-separated field names to return (e.g. 'id,clientName,total') / Campos a devolver
`offset`	No	Offset / Desplazamiento
`status`	No	Filter by quote status / Filtrar por estado
`clientId`	No	Filter by client ID / Filtrar por ID de cliente
`seriesId`	No	Filter by quote series ID / Filtrar por ID de serie

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`limit`	Yes
`total`	Yes
`offset`	Yes
`nextCursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.16.3Jul 22, 2026
Removedv1.15.2Jul 18, 2026
Changed3 schema fields changedv1.15.0Jul 11, 2026
- addedOutput schema / properties / data / items / properties / clientName / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / data / items / properties / clientName / type
```
Removed value: -"string"
```
- removedOutput schema / properties / data / items / required
```
Removed value: -[
-  "id",
-  "clientName",
-  "items"
-]
```

Changed8 schema fields changedv1.13.1Jun 17, 2026

addedInput schema / properties / after

Added value: +{
+  "description": "Cursor for cursor-based pagination (document ID) / Cursor para paginacion basada en cursor",
+  "type": "string"
+}

addedInput schema / properties / clientId

Added value: +{
+  "description": "Filter by client ID / Filtrar por ID de cliente",
+  "type": "string"
+}

addedInput schema / properties / fields

Added value: +{
+  "description": "Comma-separated field names to return (e.g. 'id,clientName,total') / Campos a devolver",
+  "type": "string"
+}

addedInput schema / properties / from

Added value: +{
+  "description": "Start date filter (YYYY-MM-DD) / Fecha inicio",
+  "type": "string"
+}

addedInput schema / properties / seriesId

Added value: +{
+  "description": "Filter by quote series ID / Filtrar por ID de serie",
+  "type": "string"
+}

addedInput schema / properties / status

Added value: +{
+  "description": "Filter by quote status / Filtrar por estado",
+  "enum": [
+    "draft",
+    "sent",
+    "accepted",
+    "rejected",
+    "expired"
+  ],
+  "type": "string"
+}

addedInput schema / properties / to

Added value: +{
+  "description": "End date filter (YYYY-MM-DD) / Fecha fin",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "clientName": {
+            "type": "string"
+          },
+          "createdAt": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "items": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "description": {
+                  "type": "string"
+                },
+                "quantity": {
+                  "type": "number"
+                },
+                "unitPrice": {
+                  "type": "number"
+                }
+              },
+              "required": [
+                "description",
+                "quantity",
+                "unitPrice"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "notes": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          },
+          "total": {
+            "type": "number"
+          },
+          "updatedAt": {
+            "type": "string"
+          },
+          "validUntil": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "clientName",
+          "items"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "limit": {
+      "type": "number"
+    },
+    "nextCursor": {
+      "type": "string"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "data",
+    "total",
+    "limit",
+    "offset"
+  ],
+  "type": "object"
+}

First observedv1.1.0Mar 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that quotes are 'proposals sent to clients before they become invoices' and lists supported statuses. No contradictions; description complements annotations well.

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 brief and front-loaded with purpose. It includes both English and Spanish, which adds length but provides clarity for multilingual users. No wasted sentences, though the bilingual repetition could be slightly trimmed for English-only agents.

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?

For a listing tool with 9 optional parameters and an output schema, the description explains the business context (quotes are proposals), supported filters, and pagination. It is complete enough for an AI agent to select and use the tool correctly.

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

Parameters4/5

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

Schema coverage is 100% with bilingual descriptions. The description adds value by grouping functionality ('optional pagination and filters') and providing a concrete example (status='sent', from='2026-01-01', limit=20). The example helps clarify usage beyond schema alone.

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 'list all quotes/estimates' with optional pagination and filters. It distinguishes quotes as proposals before invoices, differentiating from sibling tools like list_invoices and get_quote. The verb 'list' and resource 'quotes' are specific and unambiguous.

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?

The description explains when to use the tool (to list quotes with filters and pagination) and gives an example. It does not explicitly state when not to use or mention alternatives, but the context of sibling tools and the detailed description make usage clear.

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

Deploy Server