ExpenseBot

list_reports

Read-only

List the user's expense reports with pagination. Filter by status (All, Draft, Submitted, Shared). Each exact report includes its app, Bill Client, and accounting handoff URLs. Use the matching accounting URL only when the user explicitly asks to send or export that report; the app keeps organization, mapping, preview, and final confirmation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	One-based results page to return.
`limit`	No	Maximum reports to return on this page.
`filter`	No	Optional report-status filter; All returns every authorized status.	All
`clientEmail`	No	Client account email. Accountants may use this only for an accepted ExpenseBot client.

Output Schema

TableJSON Schema

Name	Required	Description
`page`	No
`limit`	No
`filter`	No
`reports`	No	Present when the user has reports.
`success`	Yes
`creationStatus`	Yes	Provenance of the listing, e.g. "existing_only".
`responseGuidance`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "creationStatus": {
+      "description": "Provenance of the listing, e.g. \"existing_only\".",
+      "type": "string"
+    },
+    "filter": {
+      "type": "string"
+    },
+    "limit": {
+      "type": "integer"
+    },
+    "page": {
+      "type": "integer"
+    },
+    "reports": {
+      "description": "Present when the user has reports.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "responseGuidance": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "creationStatus"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 25, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "description": "Standard ExpenseBot tool result envelope. `message` is the human-readable summary the AI cites; `data` is the structured payload (totals, breakdowns, ids, etc.). On failure, `success` is false and `error` carries a code/message/hint triple.",
-  "properties": {
-    "data": {
-      "additionalProperties": true,
-      "description": "Structured payload. Shape varies per tool — common keys: total, breakdown, comparison, sampleMeta, ids, expenseId, reportId, signupUrl, results.",
-      "type": "object"
-    },
-    "error": {
-      "additionalProperties": true,
-      "description": "Present only when success === false.",
-      "properties": {
-        "code": {
-          "type": "string"
-        },
-        "hint": {
-          "type": "string"
-        },
-        "message": {
-          "type": "string"
-        }
-      },
-      "type": "object"
-    },
-    "message": {
-      "description": "Human-readable result text. Always present on success; prefer rendering this verbatim before any further reasoning.",
-      "type": "string"
-    },
-    "sampleMeta": {
-      "additionalProperties": true,
-      "description": "Set when the underlying dataset was truncated. isTruncated=true means the agent saw a sample of `sampleCount` of `totalCount` rows; aggregate totals are still accurate.",
-      "properties": {
-        "isTruncated": {
-          "type": "boolean"
-        },
-        "sampleCount": {
-          "type": "integer"
-        },
-        "totalCount": {
-          "type": "integer"
-        }
-      },
-      "type": "object"
-    },
-    "success": {
-      "description": "False on tool errors; check before reading `data`.",
-      "type": "boolean"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed3 schema fields changedAug 22, 2026

addedInput schema / properties / filter / description

Added value: +"Optional report-status filter; All returns every authorized status."

addedInput schema / properties / limit / description

Added value: +"Maximum reports to return on this page."

addedInput schema / properties / page / description

Added value: +"One-based results page to return."

First observedAug 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the readOnlyHint, the description discloses that results embed accounting handoff URLs and warns against acting on them unless explicitly asked. The note that 'the app keeps organization, mapping, and final confirmation' clarifies the tool's limits, adding meaningful behavioral context.

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 short and front-loaded with the core action, followed by filter options, return contents, and a safety caveat. There is minor ambiguity in 'each exact report' and the phrase 'the app keeps organization, mapping, and final confirmation,' but overall it is efficient.

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?

For a simple read-only listing tool with an output schema, the description covers its purpose, filtering, pagination, relevant returned data, and an important usage caveat. It does not specify when to prefer sibling tools, but that is not essential for a straightforward list operation.

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%, with page, limit, filter, and clientEmail all described. The description adds only high-level context about pagination and status, and does not meaningfully extend the parameter explanations beyond what the schema already provides.

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 opens with a specific verb and resource: 'List the user's expense reports with pagination.' It is unambiguous against siblings like add_expense or export_report because the focus is purely read-only listing. The mention of status filtering and returned URLs further distinguishes it from detail or send operations.

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?

It gives a clear operational caveat—use the accounting URL only when the user explicitly asks to send/export—but it does not explicitly route an agent away from or toward sibling tools such as get_report_details or export_report. The filtering and pagination context is useful, yet alternative selection guidance is missing.

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

All ExpenseBot 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.