Skip to main content
Glama
Sign In

AskRentAI

by com.askrentai
OverviewDiscussionsAdmin

Download Attachment

download_attachment
Read-onlyIdempotent

Download and READ a Rent Manager attachment by FileID.

Returns lease documents and other files attached to a record. PDFs are rendered page-by-page so their contents can be read, not just saved, including scanned signed leases.

FileIDs come from get_tenant_notes (leases are usually filed on tenant History/Notes), get_check_attachments / get_credit_card_attachments / get_journal_attachments (invoice scans filed on a payment or GL entry), get_tenant_udfs, or get_property_udfs. The parent-record arguments tenant_id, check_id, bill_id, credit_card_transaction_id and journal_id identify the record the file hangs off; they apply when the FileID did not come from a listing earlier in the same conversation.

Long documents are returned in page chunks (pages="1-40", then pages="41-80", and so on); the result says which pages came back and what range is available next.

``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.

Input Schema

NameRequiredDescriptionDefault
pagesNo
bill_idNo
file_idNo
save_asNo
check_idNo
locationNo
as_imagesNo
max_pagesNo
tenant_idNo
journal_idNo
credit_card_transaction_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "download_attachmentOutput",
-  "type": "object"
-}New value: +null
  2. Changed2 schema fields changed
    • addedInput schema / properties / location
      Added value: +{
+  "default": "",
+  "title": "Location",
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "download_attachmentOutput",
+  "type": "object"
+}
  3. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, and the description adds meaningful context beyond them: PDFs are rendered page-by-page so contents can be read, scanned signed leases are included, long documents are chunked with page ranges reported, and the tool never fans out across Locations.

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?

The description is front-loaded with the core action and then provides practical sourcing and pagination details. It is somewhat lengthy, especially the FileID source inventory, but most of the detail is useful for invoking an 11-parameter tool correctly.

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

Completeness3/5

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

For a complex tool with 11 parameters, 0% schema description coverage, and no output schema, the description covers the central workflow but omits key parameters like save_as, as_images, and max_pages. It is adequate for the main path but not fully complete for all invocation options.

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 0% across 11 parameters, so the description must carry the full burden. It explains file_id, pages, location, and the parent-record IDs tenant_id, check_id, bill_id, credit_card_transaction_id, and journal_id, but leaves save_as, as_images, and max_pages undocumented.

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 gives a specific verb and resource: 'Download and READ a Rent Manager attachment by FileID', and clarifies that it returns lease documents and other files attached to a record. It is clear enough to distinguish from analysis tools, but it does not explicitly differentiate itself from sibling attachment tools such as download_property_attachment, download_unit_attachment, or download_invoices.

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?

It explains where FileIDs come from, when parent-record arguments are needed, and when location is required. This gives strong operational context, though it does not explicitly state when to choose this tool over the other attachment-download siblings.

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

All AskRentAI toolsInspect
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.

Resources