Skip to main content
Glama

export_report

Read-only

Get a short-lived direct PDF download for one exact authorized expense report, plus the exact highlighted in-app report link. Use the in-app report for CSV, XLSX, receipt ZIP (when available), comments, invoicing, and other visually reviewed actions. Use list_reports first to find the reportId.

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>"
    },
    "name": "export_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportIdYesReport ID from list_reports

Output Schema

NameRequiredDescriptionDefault
urlsYes
notesYes
reportYes
successYes
expiresAtYes
availableInReportYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedOutput schema / properties / expiresAt / format
      Removed value: -"date-time"
    • removedOutput schema / properties / report / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / report / properties
      Removed value: -{
      -  "id": {
      -    "type": "string"
      -  },
      -  "spreadsheetId": {
      -    "type": "string"
      -  },
      -  "status": {
      -    "type": "string"
      -  },
      -  "title": {
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / report / required
      Removed value: -[
      -  "title",
      -  "spreadsheetId"
      -]
    • removedOutput schema / properties / urls / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / urls / properties
      Removed value: -{
      -  "pdf": {
      -    "type": "string"
      -  },
      -  "report": {
      -    "type": "string"
      -  },
      -  "view": {
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / urls / required
      Removed value: -[
      -  "view",
      -  "pdf",
      -  "report"
      -]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "availableInReport": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "expiresAt": {
      +      "format": "date-time",
      +      "type": "string"
      +    },
      +    "notes": {
      +      "type": "string"
      +    },
      +    "report": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "id": {
      +          "type": "string"
      +        },
      +        "spreadsheetId": {
      +          "type": "string"
      +        },
      +        "status": {
      +          "type": "string"
      +        },
      +        "title": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "title",
      +        "spreadsheetId"
      +      ],
      +      "type": "object"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    },
      +    "urls": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "pdf": {
      +          "type": "string"
      +        },
      +        "report": {
      +          "type": "string"
      +        },
      +        "view": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "view",
      +        "pdf",
      +        "report"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "success",
      +    "report",
      +    "urls",
      +    "expiresAt",
      +    "availableInReport",
      +    "notes"
      +  ],
      +  "type": "object"
      +}
  3. 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
  4. First observed

TDQS

A4.4/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 description still adds behavior beyond that: the download URL is 'short-lived', the report must be 'authorized', and the link is 'highlighted' in-app. It stops short of describing failure behavior for unauthorized or expired reports, which keeps it off a 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 short sentences, front-loaded with the primary capability, then the exclusions, then the prerequisite. Each sentence carries a distinct instruction and nothing is repeated for padding.

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?

An output schema exists, so return values need not be explained, and the description covers scope, alternatives, and the prerequisite lookup. For a single-parameter read tool this is close to complete; only error or expiry handling for the short-lived URL is left implicit.

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% and the single reportId parameter already documents that it comes from list_reports, which the description repeats. The words 'one exact authorized expense report' reinforce that this is a single-report identifier rather than a filter, but no additional syntax or format detail is supplied. Baseline 3 is appropriate when the schema carries the parameter meaning.

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 uses a specific verb and resource ('Get a short-lived direct PDF download for one exact authorized expense report') and states exactly what comes back: a PDF URL plus the highlighted in-app report link. It also separates this tool's job from the in-app report surface, so an agent can tell what it is 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?

It gives explicit routing: use this tool for the PDF and the in-app link, but use the in-app report for CSV, XLSX, receipt ZIP, comments, and invoicing. It also states the prerequisite ordering ('Use list_reports first to find the reportId'), so both when-to-use and when-not-to-use are covered.

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.