AskRentAI

Vendor Compliance

vendor_compliance

Read-onlyIdempotent

Vendors with expired or soon-to-expire insurance / workers-comp coverage.

Runs VendorExpirationListing (report 194) and flags every vendor whose general-liability insurance or workers-comp policy is already expired or expires within days_ahead days (default 60). Use for "which vendors have expired insurance", "vendor COI compliance", "whose workers comp is lapsing", before clearing a vendor to work on site. include_missing also lists vendors with no policy date on file.

``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
`days_ahead`	No
`name_filter`	No
`include_missing`	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

A4.5/5.0

Behavior5/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 lower; the description still adds substantial operational detail: which report is executed, the 60-day default window, how include_missing changes output, per-Location labelling of results, and that unreachable Locations are reported as skipped rather than failing silently.

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?

Front-loaded with the core purpose and report name in the first line, then supporting detail. The location paragraph is dense and slightly sprawling but every clause (comma list, "all", blank semantics, skipped Locations, ID scoping) carries actionable meaning.

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

Completeness4/5

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

With an output schema present, return values needn't be described; the description still covers result labelling and skipped Locations. Combined with annotations, an agent has enough to invoke correctly; only name_filter's semantics are undocumented.

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

Parameters4/5

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

Schema coverage is 0%, so the description carries the full burden. It thoroughly documents location (ID, comma list, "all", blank default, and the ID-scoping caveat), days_ahead (default 60), and include_missing. name_filter is left entirely unexplained in both schema and description, which is the one real gap.

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?

States a specific verb and resource: flags vendors with expired/lapsing general-liability or workers-comp coverage, running VendorExpirationListing (report 194). That is clearly distinct from siblings like list_vendors (roster) and analyze_vendor_spend (spend analysis), so an agent can route correctly without opening the schema.

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

Usage Guidelines4/5

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

Provides concrete use cases ("which vendors have expired insurance", "vendor COI compliance", "whose workers comp is lapsing") plus a decision context: before clearing a vendor to work on site. It doesn't explicitly name a sibling as the alternative path for adjacent questions (e.g. general vendor listing), but the intended use is unambiguous.

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?