AskRentAI

Get Property UDFs

get_property_udfs

Read-onlyIdempotent

List all UDF values for a property, including file attachments.

``location`` (optional): a Rent Manager Location ID, a comma-separated
list, or ``"all"`` to run across every Location on this connection (see
``list_locations``). Blank = all Locations if the connection has several,
else its only Location. Output is labelled per Location; a Location that
can't be reached is listed as skipped. IDs (property, tenant, ...) belong
to one Location, so pass that Location when you filter by one.

Input Schema

Name	Required	Description	Default
`location`	No
`shortname`	No
`property_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / location

Added value: +{
+  "default": "",
+  "title": "Location",
+  "type": "string"
+}

First observedOct 19, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is met, but the description adds real value: default Location resolution when blank, per-Location labelling of output, and unreachable Locations being reported as skipped. It also warns that IDs belong to a single Location, which is non-obvious behavioral context an agent needs. Pagination or volume characteristics remain unmentioned.

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 purpose is front-loaded in one sentence, and the location detail is a single tight paragraph with no filler. Slight structural cost from inline code-markup and an appendix-like block rather than a cleanly separated parameter section.

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?

An output schema exists so return values need no explanation, and the multi-Location story is well covered. The gap is the two unaddressed parameters and the absence of any guidance on selecting this tool versus the other get_*_udfs tools, which leaves the definition only partially complete for a 3-parameter tool at 0% schema coverage.

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 0%, so the description must carry the parameter burden. It explains 'location' thoroughly (single ID, comma-separated list, 'all', blank behavior) but says nothing about 'shortname' or 'property_id', including how they interact or whether either is required to target a specific property.

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 a specific verb and resource: list UDF values for a property, including file attachments. The property scope is clear enough to distinguish it from get_tenant_udfs and get_unit_udfs by resource name, but the description never names those siblings or explicitly contrasts their scope.

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

Usage Guidelines3/5

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

Usage is implied by the resource scope, and the location paragraph gives practical guidance about when to pass a specific Location versus 'all'. However, it never says when to choose this tool over get_tenant_udfs, get_unit_udfs, or get_marketing_udfs, which are the real alternatives an agent must choose between.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AskRentAI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?