Skip to main content
Glama

Download Invoices

download_invoices
Read-onlyIdempotent

Download vendor-invoice attachments into the per-tenant FileStore.

``location`` (optional): a single Rent Manager Location ID. Required
when the connection has several Locations (see ``list_locations``);
this tool never fans out across Locations.

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": "download_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
vendorNo
end_dateNo
locationNo
portfolioNo
start_dateNo
property_idsNo
return_imagesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / location
      Added value: +{
      +  "default": "",
      +  "title": "Location",
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive on the source system, and the description adds the non-obvious side effect that files are written into a per-tenant FileStore plus the single-Location constraint. Return format and per-invoice failure behavior are still unstated, but the added context is substantive.

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?

Two short sentences, front-loaded with what the tool does, then the scoping constraint. No filler; the parenthetical cross-reference to `list_locations` earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema means return values need not be described, but with 8 parameters at 0% schema coverage the definition is far too thin: an agent cannot tell what the filters do, how dates are formatted, or what `limit` bounds. The single-parameter explanation does not cover the tool's actual surface.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 8 parameters, so the description carries the full burden, and it explains only `location`. The seven filtering/formatting parameters (`start_date`, `end_date`, `vendor`, `portfolio`, `property_ids`, `limit`, `return_images`) get no meaning, date format, or default guidance.

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 description names a specific verb and resource ('Download vendor-invoice attachments') and states the destination ('per-tenant FileStore'), which is clearly distinct from the generic download_attachment siblings. It stops short of explicitly contrasting itself with those siblings, so it is not a 5.

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

Usage Guidelines3/5

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

It gives one real usage rule: `location` is required when the connection has multiple Locations and the tool never fans out across Locations, pointing to `list_locations`. It says nothing about when to prefer this over download_attachment or how to scope the run with the date/vendor/property filters.

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.

Resources