billingo-mcp

List spendings

billingo_list_spendings

Read-onlyIdempotent

List recorded spendings, optionally filtered by start and end dates, to review costs within a specific period. Supports pagination for browsing results.

Instructions

Lists recorded spendings (costs), optionally filtered by date range.

Input Schema

Name	Required	Description
`page`	No	Page number, starting at 1.
`end_date`	No	Include spendings fulfilled on or before this date.
`per_page`	No	Results per page (1-100, default 25).
`start_date`	No	Include spendings fulfilled on or after this date.

Output Schema

Name	Required	Description	Default
`data`	Yes
`total`	No
`per_page`	No
`last_page`	No
`current_page`	No
`next_page_url`	No
`prev_page_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.3Oct 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "current_page": {
+      "type": [
+        "number",
+        "string",
+        "null"
+      ]
+    },
+    "data": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "category": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "comment": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "conversion_rate": {
+            "type": [
+              "number",
+              "string",
+              "null"
+            ]
+          },
+          "currency": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "due_date": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "fulfillment_date": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "number"
+          },
+          "invoice_date": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "invoice_number": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "paid_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "partner": {
+            "anyOf": [
+              {
+                "anyOf": [
+                  {
+                    "additionalProperties": {},
+                    "properties": {
+                      "id": {
+                        "type": [
+                          "number",
+                          "string",
+                          "null"
+                        ]
+                      },
+                      "name": {
+                        "type": [
+                          "string",
+                          "null"
+                        ]
+                      },
+                      "tax_code": {
+                        "type": [
+                          "string",
+                          "null"
+                        ]
+                      }
+                    },
+                    "type": "object"
+                  },
+                  {
+                    "items": {},
+                    "maxItems": 0,
+                    "type": "array"
+                  }
+                ]
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "payment_method": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "total_gross": {
+            "type": [
+              "number",
+              "string",
+              "null"
+            ]
+          },
+          "total_gross_local": {
+            "type": [
+              "number",
+              "string",
+              "null"
+            ]
+          },
+          "total_vat_amount": {
+            "type": [
+              "number",
+              "string",
+              "null"
+            ]
+          },
+          "total_vat_amount_local": {
+            "type": [
+              "number",
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "last_page": {
+      "type": [
+        "number",
+        "string",
+        "null"
+      ]
+    },
+    "next_page_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "per_page": {
+      "type": [
+        "number",
+        "string",
+        "null"
+      ]
+    },
+    "prev_page_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total": {
+      "type": [
+        "number",
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

First observedv0.1.0Sep 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is clear. The description adds little beyond 'recorded' and optional filtering; it does not elaborate on pagination behavior, return format, or rate limits. With annotations covering the core behavior, a 3 is appropriate.

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 a single, front-loaded sentence with no wasted words. It efficiently conveys the core action and the optional filter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, complete parameter descriptions, and clear annotations, the description is sufficient for an agent to call the tool correctly. It could mention pagination defaults, but that gap is minor because the schema covers 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%, so all four parameters (page, per_page, start_date, end_date) are fully documented in the schema. The description only restates the date-range filter and adds no semantics beyond what the schema provides. Baseline 3 is correct when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies a clear verb ('Lists') and resource ('recorded spendings (costs)'), and mentions the optional date-range filter. It distinguishes itself from the singular 'billingo_get_spending' by implication, though it does not explicitly name 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 Guidelines3/5

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

The phrase 'optionally filtered by date range' implies when to use the date parameters, but there is no explicit guidance on when to choose this tool over 'billingo_get_spending' or other list tools. Usage is implied rather than stated.

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