AskRentAI

Move-Ins and Move-Outs

move_ins_outs

Read-onlyIdempotent

Tenants who moved in or moved out in a YYYY-MM-DD date window.

``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
`end_date`	Yes
`location`	No
`portfolio`	No
`shortname`	No
`start_date`	Yes
`property_id`	No
`property_ids`	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

B3.1/5.0

Behavior4/5

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

Beyond the annotations, which already declare the tool read-only and idempotent, the description adds useful behavioral context: output is labelled per Location, unreachable Locations are reported as skipped, and tenant/property IDs are scoped to one Location. No contradiction with annotations.

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 the first sentence, and the following location guidance is relevant and reasonably sized. There is some repetition about Location scoping, but no serious bloat.

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?

The tool has seven parameters with zero schema descriptions, and the description documents only one of them. Although an output schema exists, the missing parameter documentation and lack of sibling differentiation leave significant gaps for an agent trying to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across seven parameters, so the description must carry the burden. It explains only `location` in detail and implies a date window, but leaves `portfolio`, `shortname`, `property_id`, and `property_ids` completely unexplained.

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 first sentence states a specific resource and scope: tenants who moved in or out within a date window. However, it does not distinguish this tool from the sibling `analyze_move_ins_outs`, which likely has a related but different analytical purpose.

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 explains how the `location` parameter behaves, but gives no guidance on when to use this tool versus alternatives such as `analyze_move_ins_outs`, `lease_expirations`, or `list_tenants`. The location guidance is parameter-specific, not tool-selection guidance.

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?