Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_annual_budget_comparative_report

Compare annual budget versus actuals across properties using filters like date range, property status, and GL account map.

Instructions

Returns annual budget comparative report for the given filters.

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
occurred_on_toYesThe end date for the report period (YYYY-MM-DD)
additional_account_typesNoArray of additional account types to include
gl_account_map_idNoFilter by GL account map ID
level_of_detailNoSpecify the level of detail. Defaults to "detail_view"detail_view
columnsNoArray of specific columns to include
periodsNoPeriods
Behavior1/5

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

No annotations are provided, and the description gives no behavioral details such as whether the report is read-only, any performance implications, or output format. The agent gains no insight beyond the tool's existence.

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 very short (one sentence), which is concise but at the expense of providing needed context. It is not front-loaded with critical information beyond the basic purpose.

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 11 parameters and no output schema, the description is insufficient for an agent to understand the report's scope or how to use parameters effectively. It does not explain what 'annual budget comparative' means or how filters affect output.

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?

All 11 parameters are described in the input schema (100% coverage), so the description adds no extra meaning. Baseline score of 3 is appropriate as the schema already handles parameter documentation.

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 that the tool returns an 'annual budget comparative report' for given filters. It distinguishes from some siblings (e.g., 'get_budget_comparative_report' without 'annual'), but does not explicitly differentiate from similar reports like 'get_annual_budget_forecast_report'.

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 vs. the many sibling report tools. With over 40 similar tools, the agent has no context for selecting this one.

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