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. Never call this as a preflight or follow-up to creating, sharing, or billing from a report; those tools already return the required result and links.

Input Schema

TableJSON Schema

Name	Required	Description
`reportId`	Yes	The report/spreadsheet ID
`clientEmail`	No	Client account email. Accountants may use this only for an accepted ExpenseBot client.
`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

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context: it discloses what the call returns (all expenses, totals, compliance status) and a meaningful gating rule about consent for inspection. It doesn't mention rate limits or the accountant-specific client scoping beyond the schema, hence not a full 5.

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?

Three sentences, front-loaded with the capability, then the usage condition, then the exclusion. Every sentence carries a distinct and necessary constraint with zero filler.

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 spelled out, and annotations cover safety. Combined with 100% schema coverage, the description supplies the remaining needed pieces: scope, consent gating, and the preflight/follow-up prohibition.

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 three parameters are already documented, including the analysisRequested consent semantics and the clientEmail accountant restriction. The description reinforces the consent constraint but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 (Get) and resource (full details of a specific expense report) and enumerates the payload (all expenses, totals, compliance status). It is clearly distinguishable from siblings like list_reports (enumeration) and check_compliance (single check).

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?

Explicitly states when to use it ('only when the user explicitly asks to inspect an existing report's details') and when not to ('never call this as a preflight or follow-up to creating, sharing, or billing'), explaining that those tools already return the required result and links. This is explicit when/when-not guidance with the alternative mechanism named.

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.