Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_receivables_activity_report

Generate a receivables activity report by specifying a date range and optional filters like tenant status or property groups. Uses numeric IDs for accurate results.

Instructions

Returns receivables activity report for the given filters. IMPORTANT: All ID parameters (owners_ids, properties_ids, etc.) must be numeric strings (e.g. '123'), NOT names. Use respective directory reports first to lookup IDs by name if needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tenant_visibilityNoFilter tenants by status. Defaults to "active"
tenant_statusesNoFilter by specific tenant statuses (e.g., ["0", "4"] for Current and Notice)
property_visibilityNoFilter properties by status. Defaults to "active"
propertiesNoFilter results based on properties, groups, portfolios, or owners. All ID fields must be numeric strings, not names.
receipt_date_fromYesThe start date for the reporting period based on receipt date (YYYY-MM-DD). Required.
receipt_date_toYesThe end date for the reporting period based on receipt date (YYYY-MM-DD). Required.
manually_entered_onlyNoInclude only manually entered receipts. Defaults to "0" (false)
columnsNoArray of specific columns to include in the report
Behavior2/5

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

No annotations are provided. The description does not disclose behavioral traits such as whether the tool is read-only, pagination behavior, or implications of filtering. The ID format warning is parameter-related, not behavioral. The agent is left uninformed about side effects or constraints.

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 redundant words. The first sentence states purpose, the second emphasizes a critical usage detail. Every part earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and 8 parameters, the description lacks information about the report's output format or structure. The ID lookup guidance is helpful, but missing output details reduces completeness for a complex tool.

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 described. The description adds a holistic note about ID numeric strings, but this is already present in some parameter descriptions. No new semantic meaning beyond schema is provided.

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 receivables activity report for given filters, using specific verb 'Returns' and resource 'receivables activity report'. Among many sibling report tools, this uniquely identifies its purpose.

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

Usage Guidelines4/5

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

Provides explicit guidance on parameter usage: ID parameters must be numeric strings and suggests using directory reports for ID lookup. However, it does not compare when to use this report versus other sibling reports, which would strengthen guidance.

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