Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_renewal_summary_report

Summarizes lease renewals. Filter by properties, date range, and renewal status.

Instructions

Provides a summary of lease renewals. IMPORTANT: All ID parameters (properties_ids, property_groups_ids, portfolios_ids, owners_ids) must be numeric strings (e.g. '123'), NOT names. Use respective directory reports first to lookup IDs by name if needed. NOTE: All string parameters should be properly quoted JSON strings (e.g. "active", not active).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
propertiesNoFilter results based on properties, groups, portfolios, or owners
unit_visibilityNoFilter units by status. Defaults to "active"active
start_on_fromYesThe start month for the reporting period based on lease start date (YYYY-MM). Required.
start_on_toYesThe end month for the reporting period based on lease start date (YYYY-MM). Required.
statusesNoFilter by renewal status. Defaults to ["all"]
include_tenant_transfersNoInclude tenant transfers in the report. Defaults to "0" (false)
columnsNoArray of specific columns to include in the report. Valid columns: unit_name, property, property_name, property_id, property_address, property_street, property_street2, property_city, property_state, property_zip, unit_type, unit_id, occupancy_id, tenant_name, lease_start, lease_end, previous_lease_start, previous_lease_end, previous_rent, rent, respond_by_date, renewal_sent_date, countersigned_date, automatic_renewal_date, percent_difference, dollar_difference, status, term, lease_start_month, tenant_id, tenant_tags, tenant_agent, lease_uuid, lease_document_uuid, notice_given_date, move_out. If not specified, all columns are returned.
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits like read-only nature, permissions, or error behavior. It only covers input formatting, not behavior, so transparency is low.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences plus an IMPORTANT and NOTE. It is concise with no wasted words, though the formatting notes make it slightly less structured. Still earns a high score.

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?

Given no output schema, the description does not explain return values or error handling. For a report tool, this is a gap. However, the input schema is well-covered and usage is clear, so it is adequate but incomplete.

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%, so baseline is 3. The description adds emphasis on ID format and quoting, but does not add significant meaning beyond what the schema already provides for each parameter.

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 states 'Provides a summary of lease renewals', which is a specific verb+resource. It clearly distinguishes from the many sibling report tools by focusing on renewal summary.

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

Usage Guidelines5/5

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

The description explicitly tells agents that ID parameters must be numeric strings, not names, and advises using directory reports first. It also warns about proper JSON quoting for string parameters. This is excellent usage 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