Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_aged_payables_summary_report

Retrieve aged payables summary filtered by property, group, portfolio, owner, company, balance, and as-of date.

Instructions

Returns aged payables summary for the given filters. IMPORTANT: All ID parameters must be numeric strings (e.g. '123'), NOT names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
property_visibilityNoFilter properties by statusactive
properties_idsNoFilter by specific property IDs
property_groups_idsNoFilter by property group IDs
portfolios_idsNoFilter by portfolio IDs
owners_idsNoFilter by owner IDs
occurred_onYesAs-of date (YYYY-MM-DD)
party_company_idNoFilter by company ID
balance_amountNoBalance amount to compare against
balance_comparatorNoComparison operator (e.g. "gt", "lt")
columnsNoSpecific columns to include
Behavior2/5

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

No annotations provided, so description must disclose behaviors. Only mentions ID parameter format requirement. Does not state read-only nature, permission needs, or output format. Minimal disclosure.

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?

Two sentences, no wasted words. Critical usage note is front-loaded in second sentence. Efficient and clear.

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?

Despite 10 parameters and no output schema, description is very brief. Does not explain report scope, typical use cases, or output structure. Lacks guidance for selecting among 46 sibling report tools. Incomplete for its complexity.

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 description coverage is 100% (all parameters described). Description adds critical value by clarifying that all ID parameters must be numeric strings, a constraint not obvious from schema type 'string'. This prevents misuse.

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?

States it returns an aged payables summary for given filters. Verb and resource clear. Does not differentiate from sibling reports like get_aged_receivables_detail_report, but the name itself indicates payables focus.

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 on when to use this tool vs alternatives among many sibling report tools. Only provides a parameter constraint note, no context for selection.

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