Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_delinquency_as_of_report

Retrieve a delinquency as-of report for specified properties, date, and filters. Use numeric IDs for properties and filter by tenant status, balance, or tags.

Instructions

Returns delinquency as of report for the given filters. IMPORTANT: All ID parameters (properties_ids, etc.) must be numeric strings (e.g. '123'), NOT names. Use respective directory reports first to lookup IDs by name if needed. NOTE: tenant_statuses uses numeric codes: 0=Current, 1=Past, 2=Future, 3=Evict, 4=Notice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
property_visibilityNoFilter properties by status. Defaults to "active".active
propertiesNoOptional. Filter by specific property-related IDs.
occurred_on_toYesRequired. Date to run the report as of in YYYY-MM-DD format.
delinquency_note_rangeNoOptional. Filter by delinquency note range.
tenant_statusesNoFilter by tenant status. Valid values: "0"=Current, "1"=Past, "2"=Future, "3"=Evict, "4"=Notice. Defaults to ["0", "4"] (Current and Notice tenants).
tagsNoOptional. Filter by property tags.
amount_owed_in_accountNoFilter by amount owed in account. Defaults to "all".all
balance_operatorNoOptional. Filter by balance amount with comparison operator.
columnsNoArray of specific columns to include in the report. Valid columns: unit, name, tenant_status, tags, phone_numbers, move_in, move_out, primary_tenant_email, unit_type, property, property_name, property_id, property_address, property_street, property_street2, property_city, property_state, property_zip, amount_receivable, delinquent_subsidy_amount, 00_to30, 30_plus, 30_to60, 60_plus, 60_to90, 90_plus, this_month, last_month, month_before_last, delinquent_rent, delinquency_notes, certified_funds_only, in_collections, collections_agency, unit_id, occupancy_id, property_group_id
Behavior3/5

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

No annotations provided. The description adds behavioral context by requiring numeric strings for IDs and clarifying status codes, but does not disclose read-only nature, auth requirements, or other behavioral traits.

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 concise sentences: first states purpose, then two bullet-pointed notes. Front-loaded with main action, no wasted words.

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?

For a report tool with 9 parameters (nested objects) and no output schema, the description covers key operational details. Could mention the report output format or that columns parameter controls data, but overall complete enough.

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%, baseline 3. The description adds critical value by specifying that ID parameters must be numeric strings (not names) and explaining tenant_statuses codes, which goes beyond the schema's type definitions.

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 clearly states the tool returns a 'delinquency as of report' (specific verb and resource). The sibling tools are all different report names, so this description distinguishes it sufficiently.

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?

No explicit guidance on when to use this report vs. siblings. The description provides important operational notes (ID format, tenant status codes) but not comparative usage advice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CryptoCultCurt/appfolio-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server