Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_vendor_directory_report

Retrieve a directory of vendors filtered by insurance expirations, tags, visibility, and payment type. Generate a customizable vendor report for property management.

Instructions

Retrieves a directory of vendors. IMPORTANT: All ID parameters must be numeric strings (e.g. '123'), NOT names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workers_comp_expiration_toNoOptional. Filter vendors whose Workers Comp expires on or before this date (YYYY-MM-DD).
liability_expiration_toNoOptional. Filter vendors whose Liability Insurance expires on or before this date (YYYY-MM-DD).
epa_expiration_toNoOptional. Filter vendors whose EPA Certification expires on or before this date (YYYY-MM-DD).
auto_insurance_expiration_toNoOptional. Filter vendors whose Auto Insurance expires on or before this date (YYYY-MM-DD).
state_license_expiration_toNoOptional. Filter vendors whose State License expires on or before this date (YYYY-MM-DD).
contract_expiration_toNoOptional. Filter vendors whose Contract expires on or before this date (YYYY-MM-DD).
tagsNoOptional. Filter by a comma-separated list of tags (e.g., "plumbing,hvac").
vendor_visibilityNoFilter vendors by status. Defaults to "active"active
payment_typeNoOptional. Filter by payment type (eCheck, Check, or all). Defaults to all if not specified.
created_byNoFilter by who created the vendor. Defaults to "All".All
vendor_typeNoFilter by vendor type. Defaults to "All".All
columnsNoArray of specific columns to include in the report
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as data freshness, pagination, or permissions required. The tool's behavior beyond 'retrieves a directory' is completely opaque.

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

Conciseness2/5

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

The description is short but wastes space with a misleading note about ID parameters that do not exist in the schema. It is not effectively concise.

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

Completeness1/5

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

With 12 parameters and no output schema or annotations, the description is severely incomplete. It does not explain the return format, how to interpret the directory, or any edge cases.

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 description coverage is 100%, so all 12 parameters already have descriptions in the schema. The description adds no additional meaning beyond the schema, resulting in a baseline score.

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 'Retrieves a directory of vendors,' which is a specific verb+resource. Among many sibling report tools, this one is uniquely identified as a vendor directory.

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?

The description includes an important note about ID parameters, but the input schema contains no ID parameters, making the note irrelevant. There is no guidance on when to use this tool versus alternatives like get_vendor_ledger_report.

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