Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_cashflow_12_month_report

Generates a 12-month cash flow report for properties, filtering by dates, property status, owners, and portfolios to analyze income and expenses.

Instructions

Generates a 12-month cash flow report.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
property_visibilityNoFilter properties by status. Defaults to "active"active
properties_idsNoFilter by specific property IDs
property_groups_idsNoFilter by property group IDs
portfolios_idsNoFilter by portfolio IDs
owners_idsNoFilter by owner IDs
posted_on_fromYesRequired. The start month for the reporting period (YYYY-MM).
posted_on_toYesRequired. The end month for the reporting period (YYYY-MM).
gl_account_map_idNoOptional. Filter by a specific GL Account Map ID.
level_of_detailNoLevel of detail. Defaults to "detail_view"detail_view
include_zero_balance_gl_accountsNoInclude GL accounts with zero balance. Defaults to "0"0
exclude_suppressed_feesNoExclude suppressed fees. Defaults to "0"0
columnsNoArray of specific columns to include
Behavior2/5

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

With no annotations, the description carries full burden. It only states the generic action without disclosing read-only nature, potential resource consumption, or other behavioral traits beyond what is obvious.

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 description is a single sentence, making it concise. However, it lacks necessary detail, so it is not optimally informative for its length.

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?

Given the complexity of 12 parameters and no output schema, the description should summarize the report's purpose and how filters impact it. The current description is too vague to be complete.

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% with each parameter having a description. The description adds no additional meaning to the parameters beyond what the schema provides, so baseline 3 is appropriate.

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 generates a 12-month cash flow report, which is a specific verb+resource combination. It distinguishes from sibling tools like get_cashflow_report which may cover different periods.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, nor does it mention required parameters or preconditions. There is no explicit context for usage.

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