ExpenseBot

get_report_details

Read-only

Get full details of a specific expense report including all expenses, totals, and compliance status. Use only when the user explicitly asks to inspect an existing report's details. Without checkFreshness:true, returns the stored report only. When explicitly requested together with analysisRequested:true, freshness reads canonical Google Sheets sources with a 5-second bound; if full tax-year replay is unavailable, status is unknown, not current. Never call this as a preflight or follow-up to creating, sharing, or billing from a report; those tools already return the requested result and links.

Input Schema

Name	Required	Description
`reportId`	Yes	The report/spreadsheet ID
`clientEmail`	No	Accepted client's account email (accountants only).
`checkFreshness`	No	Set true only when the user explicitly asks whether this Year End report is current. Requires analysisRequested:true; runs a bounded Google Sheets source check and may return unknown. Never use after report creation, sharing, or billing.
`analysisRequested`	Yes	Set true only when the user explicitly asked to inspect this report. Do not ask for or copy their full message, and do not infer consent from report creation, sharing, or billing.

Output Schema

Name	Required	Description
`report`	Yes	The full stored report record.
`success`	Yes
`freshness`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026

changedInput schema / properties / checkFreshness / description

Previous value: -"Set true only when the user explicitly asks whether this existing Year End report is current. Requires analysisRequested:true and performs a bounded Google Sheets source check; may return unknown if full tax-year replay is unavailable. Never use after report creation, sharing, or billing."New value: +"Set true only when the user explicitly asks whether this Year End report is current. Requires analysisRequested:true; runs a bounded Google Sheets source check and may return unknown. Never use after report creation, sharing, or billing."

changedInput schema / properties / clientEmail / description

Previous value: -"Client account email. Accountants may use this only for an accepted ExpenseBot client."New value: +"Accepted client's account email (accountants only)."

Changed2 schema fields changedOct 16, 2026

addedInput schema / properties / checkFreshness

Added value: +{
+  "description": "Set true only when the user explicitly asks whether this existing Year End report is current. Requires analysisRequested:true and performs a bounded Google Sheets source check; may return unknown if full tax-year replay is unavailable. Never use after report creation, sharing, or billing.",
+  "enum": [
+    true
+  ],
+  "type": "boolean"
+}

addedOutput schema / properties / freshness

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "checkedAt": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "reportUrl": {
+      "format": "uri",
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "current",
+        "outdated",
+        "unknown",
+        "not_applicable"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "checkedAt",
+    "message",
+    "reportUrl"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedOct 5, 2026

addedInput schema / properties / analysisRequested

Added value: +{
+  "description": "Set true only when the user explicitly asked to inspect this report. Do not ask for or copy their full message, and do not infer consent from report creation, sharing, or billing.",
+  "enum": [
+    true
+  ],
+  "type": "boolean"
+}

removedInput schema / properties / userRequest

Removed value: -{
-  "description": "The user's exact request asking to inspect this report. Do not paraphrase or invent diagnostic intent.",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "reportId",
-  "userRequest"
-]New value: +[
+  "reportId",
+  "analysisRequested"
+]

Changed1 schema field changedSep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "report": {
+      "additionalProperties": true,
+      "description": "The full stored report record.",
+      "type": "object"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "report"
+  ],
+  "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

First observedAug 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: it discloses that the default path reads only the stored report, that the freshness path hits canonical Google Sheets sources under a 5-second bound, and that an incomplete tax-year replay yields 'unknown' rather than 'current'. That degraded-result semantics is exactly the kind of behavior an agent cannot infer from structured fields.

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?

Front-loaded with the resource and its payload, then the gating rules, then the exception path — a sound ordering with no filler. The freshness sentence restates some of what the schema already says about analysisRequested, which is the only redundancy.

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?

Complete for a four-parameter read tool with an output schema: return shape needn't be described, and the description instead spends its budget on the non-obvious parts — consent requirements, the freshness escalation, and the unknown-vs-current failure mode. Nothing needed to invoke it correctly is missing.

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%, so the baseline is 3, but the description adds genuine meaning: it ties checkFreshness to a bounded source check, explains the unknown-status outcome, and reinforces that analysisRequested must reflect explicit user intent. clientEmail (accountants-only) is not mentioned in the description, leaving one parameter to the 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?

States a specific verb and resource ('Get full details of a specific expense report') plus the payload it returns: all expenses, totals, and compliance status. It also carves itself out from the write-side siblings (create, share, bill) by declaring it is never a preflight or follow-up to those, so an agent can place it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit positive condition ('only when the user explicitly asks to inspect an existing report's details') and an explicit negative one ('Never call this as a preflight or follow-up to creating, sharing, or billing'). The checkFreshness escalation has its own trigger condition, so both the default and the elevated path are routable.

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.