Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_fixed_assets_report

Retrieve a filtered report of fixed assets by property, unit, asset type, and status, including property-level assets.

Instructions

Returns a report of fixed assets based on the provided filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
property_visibilityNoFilter properties by status. Defaults to "active"active
unit_idsNoArray of unit IDs to filter by
propertyNoFilter by a specific property ID
include_property_level_fixed_assetsNoInclude assets linked directly to the property. Defaults to "1" (true)1
asset_typesNoFilter by specific asset type name. Defaults to "All"All
statusNoFilter by asset status. Defaults to "all"all
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, so the description must convey behavioral traits. It only states 'returns a report' without mentioning read-only nature, permissions, output format, or pagination, leaving important gaps.

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 concise (one sentence) but lacks necessary detail. While not verbose, it sacrifices completeness for brevity.

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?

With 7 parameters, no output schema, and many sibling tools, the description is insufficient. It omits details on output format, filtering behavior, and when to use this report over others.

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 has 100% coverage with descriptions for each parameter. The tool description adds no additional meaning beyond what the schema already provides, so baseline of 3 is appropriate.

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 the tool returns a report of fixed assets based on filters, which is a specific verb+resource. It distinguishes from other report siblings by focusing on fixed assets.

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 versus other report tools. With many sibling tools, the lack of differentiation or context is a significant gap.

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