Skip to main content
Glama

get_spreadsheet_url

Read-only

Return the master Google Sheet and authenticated workspace links, including Year-End. Show only 1–2 relevant links. Open spreadsheet: Sheet. Receipt added: Review expenses + Sheet; income added: Review income + Sheet. Receipts needing review: reviewReceiptsUrl. Held upload: use its Review files link. Gmail scan/connection: Scan Gmail. Bank/card: Reconcile. Configuration: Automation Hub/General Settings. Category/G/L/account codes: Category management. Client/project/trip groups: Group management. Personal classification: Personal rules. Client billing: use returned clientBillingHandoffs: manageClients, tagReadyExpenses, createClientReport. Named client grouping: search_expenses then group_expenses. Google Photos: authenticated picker with consent. Receipt storage: returned Drive folder only; never invent a folder ID. Complete unambiguous cash expense/mileage: direct write tool. Multiple/incomplete expenses, credits/refunds, tax/tip/per diem or visual review: Manual expense. Route/repeated/calendar/rideshare mileage, per diem or review: Mileage and travel. Income file without chat attachment or complex review: Import income (previews every row). Team setup: role-aware handoff; explain owner-access requirements. Complex reports: Create report. Read-only; no row changes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_spreadsheet_url"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes
messageYes
successYes
reportsUrlYes
yearEndUrlNoAuthenticated Year-End screen link.
dashboardUrlYes
gmailScanUrlYes
spreadsheetIdYes
spreadsheetUrlYes
reviewIncomeUrlYes
reviewExpensesUrlYes
reviewReceiptsUrlNo
gmailActionNeededUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / data / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / spreadsheetId / minLength
      Removed value: -1
  2. Changed1 schema field changed
    • addedOutput schema / properties / reviewReceiptsUrl
      Added value: +{
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / yearEndUrl
      Added value: +{
      +  "description": "Authenticated Year-End screen link.",
      +  "type": "string"
      +}
  4. Changed16 schema fields changed
    • removedOutput schema / description
      Removed value: -"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."
    • addedOutput schema / properties / dashboardUrl
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / data / description
      Removed value: -"Structured payload. Shape varies per tool — common keys: total, breakdown, comparison, sampleMeta, ids, expenseId, reportId, signupUrl, results."
    • removedOutput schema / properties / error
      Removed value: -{
      -  "additionalProperties": true,
      -  "description": "Present only when success === false.",
      -  "properties": {
      -    "code": {
      -      "type": "string"
      -    },
      -    "hint": {
      -      "type": "string"
      -    },
      -    "message": {
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}
    • addedOutput schema / properties / gmailActionNeededUrl
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / gmailScanUrl
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / message / description
      Removed value: -"Human-readable result text. Always present on success; prefer rendering this verbatim before any further reasoning."
    • addedOutput schema / properties / reportsUrl
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / reviewExpensesUrl
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / reviewIncomeUrl
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / sampleMeta
      Removed value: -{
      -  "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"
      -}
    • addedOutput schema / properties / spreadsheetId
      Added value: +{
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedOutput schema / properties / spreadsheetUrl
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / success / const
      Added value: +true
    • removedOutput schema / properties / success / description
      Removed value: -"False on tool errors; check before reading `data`."
    • addedOutput schema / required
      Added value: +[
      +  "success",
      +  "spreadsheetId",
      +  "spreadsheetUrl",
      +  "reviewExpensesUrl",
      +  "reviewIncomeUrl",
      +  "gmailScanUrl",
      +  "gmailActionNeededUrl",
      +  "reportsUrl",
      +  "dashboardUrl",
      +  "data",
      +  "message"
      +]
  5. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the trailing 'Read-only; no row changes' merely repeats them. Beyond that, the description adds genuinely useful behavioral context: links are authenticated, receipt storage must use the returned Drive folder and never an invented folder ID, Google Photos uses an authenticated picker with consent, Import income previews every row, and team setup requires explaining owner-access requirements. An output schema exists, so the absence of return-value detail is acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is front-loaded and the content is dense with no filler, but the body is a single unstructured run-on of 'topic: tool' fragments that is hard to scan and mixes this tool's behavior with routing rules for unrelated tools. Several entries (client billing handoffs, named client grouping, complex reports) are only tangentially related to returning spreadsheet URLs. It is information-rich but poorly structured for an agent parsing it quickly.

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?

With zero parameters, full annotation coverage and an output schema, the burden is light, and the description still covers authentication, link volume, and the main handoff destinations. The remaining gap is minor: it does not say whether links are stable across sessions or what to do if a link fails to open.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not waste space restating an empty schema.

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 opening sentence gives a specific verb and resource: return the master Google Sheet plus authenticated workspace links, including Year-End. That is enough to tell it apart from the get_* data tools in the sibling list, which return metrics rather than URLs. The purpose is only stated once at the top and then buried under a routing table, so it is clear but not reinforced.

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

Usage Guidelines4/5

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

The description is unusually explicit about when to surface which link ('Receipt added: Review expenses + Sheet; income added: Review income + Sheet') and routes a dozen adjacent needs to named alternatives (Reconcile, Automation Hub, Category management, Import income, Manual expense, Mileage and travel). It even constrains output volume ('Show only 1–2 relevant links'). What it lacks is an explicit statement of when NOT to call this tool, or whether it should be called proactively at the start of a session.

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.