Maqui Analytics

Ventas

get_sales

Read-only

[DEMO SINTÉTICA] Ventas del restaurante registradas en Fudo (sistema POS gastronómico): total facturado, cantidad de tickets, ticket promedio, desglose por canal (Local, Delivery, Mostrador). Sirve para "ventas", "facturación", "ingresos", "tickets", "qué vendimos". Solo disponible para restaurantes/locales con Fudo conectado.

Input Schema

Name	Required	Description	Default
`date_range`	No	Período a consultar. Ejemplos: "últimos 30 días", "enero 2025", "2025-01-01 a 2025-01-31", "este mes", "mes pasado". Por defecto: últimos 30 días.

Output Schema

Name	Required	Description
`data`	Yes
`demo`	No	Solo aparece en demo; todos sus datos son ficticios.
`notice`	No	Aviso obligatorio de datos sintéticos cuando demo es true.
`sample_period`	No	Período fijo de los ejemplos sintéticos; no cambia al solicitar otro rango.
`requested_period`	No	Rango solicitado a la demo; no es el período real de sus ejemplos.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "description": "Estadísticas de la cuenta autenticada en data. Si demo es true, son ejemplos sintéticos; sample_period es su período y requested_period solo el rango solicitado.",
+  "properties": {
+    "data": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "description": "Ventas registradas en Fudo, no conversiones publicitarias.",
+          "properties": {
+            "byChannel": {
+              "additionalProperties": false,
+              "description": "Desglose de los tres canales conocidos; otros tipos pueden quedar fuera del desglose.",
+              "properties": {
+                "delivery": {
+                  "additionalProperties": false,
+                  "description": "Ventas de este canal.",
+                  "properties": {
+                    "total": {
+                      "description": "Facturación en la moneda del POS.",
+                      "type": "number"
+                    },
+                    "ventas": {
+                      "description": "Cantidad de tickets cerrados.",
+                      "type": "number"
+                    }
+                  },
+                  "required": [
+                    "ventas",
+                    "total"
+                  ],
+                  "type": "object"
+                },
+                "local": {
+                  "additionalProperties": false,
+                  "description": "Ventas de este canal.",
+                  "properties": {
+                    "total": {
+                      "description": "Facturación en la moneda del POS.",
+                      "type": "number"
+                    },
+                    "ventas": {
+                      "description": "Cantidad de tickets cerrados.",
+                      "type": "number"
+                    }
+                  },
+                  "required": [
+                    "ventas",
+                    "total"
+                  ],
+                  "type": "object"
+                },
+                "mostrador": {
+                  "additionalProperties": false,
+                  "description": "Ventas de este canal.",
+                  "properties": {
+                    "total": {
+                      "description": "Facturación en la moneda del POS.",
+                      "type": "number"
+                    },
+                    "ventas": {
+                      "description": "Cantidad de tickets cerrados.",
+                      "type": "number"
+                    }
+                  },
+                  "required": [
+                    "ventas",
+                    "total"
+                  ],
+                  "type": "object"
+                }
+              },
+              "required": [
+                "local",
+                "delivery",
+                "mostrador"
+              ],
+              "type": "object"
+            },
+            "period": {
+              "additionalProperties": false,
+              "description": "Rango consultado, desde from hasta to inclusive.",
+              "properties": {
+                "from": {
+                  "description": "Fecha YYYY-MM-DD.",
+                  "format": "date",
+                  "type": "string"
+                },
+                "to": {
+                  "description": "Fecha YYYY-MM-DD.",
+                  "format": "date",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "from",
+                "to"
+              ],
+              "type": "object"
+            },
+            "ticketPromedio": {
+              "description": "Promedio por ticket cerrado en moneda del POS, redondeado.",
+              "type": "number"
+            },
+            "totalFacturado": {
+              "description": "Facturación de tickets cerrados en moneda del POS, redondeada.",
+              "type": "number"
+            },
+            "totalVentas": {
+              "description": "Tickets cerrados registrados en Fudo.",
+              "type": "number"
+            }
+          },
+          "required": [
+            "period",
+            "totalVentas",
+            "totalFacturado",
+            "ticketPromedio",
+            "byChannel"
+          ],
+          "type": "object"
+        },
+        {
+          "additionalProperties": false,
+          "description": "Sin datos de ventas; no afirmar ingresos cero sin verificar cobertura del POS.",
+          "properties": {
+            "message": {
+              "description": "Aviso de que no hay datos de ventas para el período.",
+              "type": "string"
+            },
+            "period": {
+              "additionalProperties": false,
+              "description": "Rango consultado, desde from hasta to inclusive.",
+              "properties": {
+                "from": {
+                  "description": "Fecha YYYY-MM-DD.",
+                  "format": "date",
+                  "type": "string"
+                },
+                "to": {
+                  "description": "Fecha YYYY-MM-DD.",
+                  "format": "date",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "from",
+                "to"
+              ],
+              "type": "object"
+            }
+          },
+          "required": [
+            "period",
+            "message"
+          ],
+          "type": "object"
+        }
+      ]
+    },
+    "demo": {
+      "const": true,
+      "description": "Solo aparece en demo; todos sus datos son ficticios.",
+      "type": "boolean"
+    },
+    "notice": {
+      "description": "Aviso obligatorio de datos sintéticos cuando demo es true.",
+      "type": "string"
+    },
+    "requested_period": {
+      "additionalProperties": false,
+      "description": "Rango solicitado a la demo; no es el período real de sus ejemplos.",
+      "properties": {
+        "from": {
+          "description": "Fecha YYYY-MM-DD.",
+          "format": "date",
+          "type": "string"
+        },
+        "to": {
+          "description": "Fecha YYYY-MM-DD.",
+          "format": "date",
+          "type": "string"
+        }
+      },
+      "required": [
+        "from",
+        "to"
+      ],
+      "type": "object"
+    },
+    "sample_period": {
+      "additionalProperties": false,
+      "description": "Período fijo de los ejemplos sintéticos; no cambia al solicitar otro rango.",
+      "properties": {
+        "from": {
+          "description": "Fecha YYYY-MM-DD.",
+          "format": "date",
+          "type": "string"
+        },
+        "to": {
+          "description": "Fecha YYYY-MM-DD.",
+          "format": "date",
+          "type": "string"
+        }
+      },
+      "required": [
+        "from",
+        "to"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

First observedMay 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: the upstream data source (Fudo POS), the precondition that Fudo must be connected, and the synthetic/demo nature of the data — all of which affect whether results can be trusted.

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, front-loaded with the payload contents, followed by the usage triggers and the availability caveat. The [DEMO SINTÉTICA] prefix is the only overhead and it carries real information about data provenance.

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?

An output schema exists so return values need not be explained, annotations cover the safety profile, and the one parameter is fully described in the schema. The description fills the remaining gaps — data source, prerequisites, and intended query phrases — leaving nothing an agent needs before invoking it.

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% and the single optional date_range parameter is fully documented with examples and a default, so the schema does the heavy lifting. The description adds no additional semantics about the period parameter, which is the expected baseline when coverage is complete.

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?

States a specific verb+resource (sales recorded in Fudo POS) and enumerates the exact metrics returned: total billed, ticket count, average ticket, and channel breakdown (Local, Delivery, Mostrador). This clearly separates it from the sibling tools, which are all ad/analytics-platform summaries rather than POS revenue.

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?

Gives explicit trigger vocabulary ("ventas", "facturación", "ingresos", "tickets", "qué vendimos") and a hard availability condition: only for restaurants/locations with Fudo connected. It does not name an alternative tool or an exclusion case, which keeps it below a 5.

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

All Maqui Analytics tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.