Skip to main content
Glama

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "reportId": "<reportId>",
      "analysisRequested": "<analysisRequested>"
    },
    "name": "get_report_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportIdYesThe report/spreadsheet ID
clientEmailNoAccountants: accepted client email only.
checkFreshnessNoTrue only when the user explicitly asks if this Year End report is current. Needs analysisRequested:true; a bounded Sheets check that may return unknown. Never after report creation, sharing or billing.
analysisRequestedYesTrue only when the user explicitly asked to inspect this report. Never ask for or copy their message or infer consent from report creation, sharing or billing.

Output Schema

NameRequiredDescriptionDefault
reportYesThe full stored report record.
successYes
freshnessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / freshness / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / freshness / properties
      Removed value: -{
      -  "checkedAt": {
      -    "format": "date-time",
      -    "type": "string"
      -  },
      -  "message": {
      -    "type": "string"
      -  },
      -  "reportUrl": {
      -    "format": "uri",
      -    "type": "string"
      -  },
      -  "status": {
      -    "enum": [
      -      "current",
      -      "outdated",
      -      "unknown",
      -      "not_applicable"
      -    ],
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / freshness / required
      Removed value: -[
      -  "status",
      -  "checkedAt",
      -  "message",
      -  "reportUrl"
      -]
    • removedOutput schema / properties / report / additionalProperties
      Removed value: -true
  2. Changed2 schema fields changed
    • changedInput schema / properties / analysisRequested / description
      Previous value: -"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."New value: +"True only when the user explicitly asked to inspect this report. Never ask for or copy their message or infer consent from report creation, sharing or billing."
    • changedInput schema / properties / checkFreshness / description
      Previous 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."New value: +"True only when the user explicitly asks if this Year End report is current. Needs analysisRequested:true; a bounded Sheets check that may return unknown. Never after report creation, sharing or billing."
  3. Changed1 schema field changed
    • changedInput schema / properties / clientEmail / description
      Previous value: -"Accepted client's account email (accountants only)."New value: +"Accountants: accepted client email only."
  4. Changed2 schema fields changed
    • 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)."
  5. Changed2 schema fields changed
    • 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"
      +}
  6. Changed3 schema fields changed
    • 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"
      +]
  7. Changed1 schema field changed
    • 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"
      +}
  8. Changed1 schema field changed
    • 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
  9. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Well beyond the annotations (readOnly, non-destructive, open-world): it discloses that the default path returns the stored report only, that the freshness path reads canonical Google Sheets under a 5-second bound, and that status can come back 'unknown' rather than 'current'. The remaining gap is that it says nothing about result size or pagination for a full-detail report, which matters for an agent deciding whether to call it.

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 purpose, then the usage gate, then the freshness behavior, then the exclusions — a logical order with no filler sentences. It is dense and repeats 'explicitly' several times, which costs a little readability but each clause carries distinct guidance.

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?

For a read tool with full annotation coverage, a 100%-documented schema, and an output schema that explains return values, nothing material is missing. Consent requirements, freshness caveats, and the prohibition on using it around create/share/billing calls are all stated.

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 would be 3, but the description adds real meaning on top: the consequence of omitting checkFreshness (stored report only) and the effect of combining it with analysisRequested (bounded canonical Sheets read with a possible unknown status). It also reinforces the consent semantics of analysisRequested that the schema states.

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') and enumerates the payload an agent receives: all expenses, totals, and compliance status. That scope cleanly separates it from lookup tools like get_expense_by_id and summary tools like get_spending_summary.

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 gate ('Use only when the user explicitly asks to inspect an existing report's details') and explicit exclusions ('Never call this as a preflight or follow-up to creating, sharing, or billing'). It also conditions the freshness path on the user explicitly asking whether the report is current.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.