Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_income_statement_date_range_report

Generate an income statement report for a specific date range, with optional filters for properties, portfolios, and accounts.

Instructions

Returns the income statement report for a specified date range.

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_fromYesStart date for the posting period (YYYY-MM-DD) - Required
posted_on_toYesEnd date for the posting period (YYYY-MM-DD) - Required
gl_account_map_idNoFilter by a specific GL account map ID
level_of_detailNoSpecify the level of detail. Defaults to "detail_view"detail_view
include_zero_balance_gl_accountsNoInclude GL accounts with zero balance. Defaults to "0"0
fund_typeNoFilter by fund type. Defaults to "all"all
columnsNoArray of specific columns to include
Behavior2/5

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

No annotations are present, and the description does not disclose any behavioral traits such as read-only nature, side effects, rate limits, or pagination. The agent cannot infer safety or performance characteristics.

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 one sentence and very concise, but it lacks necessary detail to fully inform the agent. It is front-loaded but under-specified.

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 12 parameters, no output schema, and no annotations, the description fails to provide complete context. It does not explain return structure, data format, or any constraints beyond the schema.

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 descriptions for each parameter. The tool description adds no new parameter information beyond the schema, meeting the baseline for high coverage but not exceeding it.

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 clearly states it returns an income statement report for a specified date range. However, it does not differentiate from the sibling tool get_income_statement_12_month_report, leaving ambiguity about when to use each.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, when not to use it, or comparison with sibling tools.

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