Frihet MCP Server

List Clients

list_clients

Read-onlyIdempotent

List clients with pagination, search, and CRM stage filters. Returns contact info, tax IDs, and addresses.

Instructions

List all clients/customers with optional pagination. Returns contact info, tax IDs, and addresses. / Lista todos los clientes con paginacion opcional. Devuelve informacion de contacto, NIF/CIF y direcciones.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Search by name or email / Buscar por nombre o email
`after`	No	Cursor for cursor-based pagination (document ID) / Cursor para paginacion basada en cursor
`limit`	No	Max results (1-100) / Resultados maximos
`stage`	No	Filter by CRM stage / Filtrar por etapa del CRM
`fields`	No	Comma-separated field names to return (e.g. 'id,name,email') / Campos a devolver
`offset`	No	Offset / Desplazamiento

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
Changed1 schema field changedv1.15.0Jul 11, 2026
- removedOutput schema / properties / data / items / required
```
Removed value: -[
-  "id",
-  "name"
-]
```

Changed5 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 / fields

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

addedInput schema / properties / q

Added value: +{
+  "description": "Search by name or email / Buscar por nombre o email",
+  "type": "string"
+}

addedInput schema / properties / stage

Added value: +{
+  "description": "Filter by CRM stage / Filtrar por etapa del CRM",
+  "enum": [
+    "lead",
+    "contacted",
+    "proposal",
+    "active",
+    "inactive",
+    "lost"
+  ],
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "address": {
+            "additionalProperties": false,
+            "properties": {
+              "city": {
+                "type": "string"
+              },
+              "country": {
+                "type": "string"
+              },
+              "postalCode": {
+                "type": "string"
+              },
+              "state": {
+                "type": "string"
+              },
+              "street": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "createdAt": {
+            "type": "string"
+          },
+          "email": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "phone": {
+            "type": "string"
+          },
+          "taxId": {
+            "type": "string"
+          },
+          "updatedAt": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name"
+        ],
+        "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.1/5.0

Behavior4/5

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

Description aligns with annotations (readOnly, idempotent, non-destructive) and adds value by specifying return content (contact info, tax IDs, addresses). No contradictions.

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?

Two sentences in English and Spanish, no wasted words, front-loaded with key 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?

Lacks mention of field selection ('fields' parameter) and filtering ('stage'), which are important for agent to know. Output schema exists but description could be more comprehensive.

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 coverage is 100%, so baseline is 3. Description does not add significant insight beyond schema, e.g., omitting mention of 'fields' or 'stage' parameters.

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?

Description clearly states verb 'List', resource 'clients/customers', and scope 'all with optional pagination', distinguishing it from sibling tools like get_client.

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?

Mentions optional pagination and return fields, but lacks explicit guidance on when to use this vs. get_client for a single client or other list tools.

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

Deploy Server