AskRentAI

List Vendors

list_vendors

Read-onlyIdempotent

List the AP vendor master — who our vendors are, category, 1099 status.

Sourced from /Vendors. Complements analyze_vendor_spend (payment totals) and vendor_compliance (insurance/COI expiry) with the roster: vendor names, categories, whether each has a Tax ID on file (1099-ready), active status. Use for "list our vendors", "which vendors do we have", "vendors in the plumbing category", "which vendors are missing a W-9/Tax ID". Filter by name_filter / category_filter; active_only hides inactive vendors.

``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
`active_only`	No
`name_filter`	No
`category_filter`	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

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavior: multi-Location fan-out, per-Location labelling of output, and that unreachable Locations are reported as skipped rather than failing the call. It does not discuss rate limits or result-size/pagination behavior, keeping it short of a 5.

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?

Purpose, differentiation, and use cases are front-loaded in the first three sentences; the location paragraph trails as a scoped note. The location block is verbose and carries some markup noise ('``location``') but the length is defensible for a multi-Location fan-out tool.

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?

An output schema exists, so return values need no explanation, and the description covers source, scope, filtering, and multi-Location behavior. The only substantive omission for an agent to call it correctly is how the two text filters match.

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?

With 0% schema description coverage the description must carry the load, and it largely does: location is explained in depth (single ID, comma list, or "all", plus the blank/default rule and the caveat that IDs belong to one Location), and active_only's effect is stated. Gaps remain — the matching semantics of name_filter/category_filter (substring vs exact) and active_only defaulting to true are never spelled out.

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 ('List the AP vendor master') plus the exact fields returned (names, categories, Tax ID/1099 status, active status) and the source endpoint (/Vendors). It explicitly positions itself against the two nearest siblings, analyze_vendor_spend (payment totals) and vendor_compliance (COI expiry), so an agent can route correctly without opening a schema.

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

Usage Guidelines5/5

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

Provides concrete trigger phrases ('list our vendors', 'vendors in the plumbing category', 'which vendors are missing a W-9/Tax ID') and names the alternative tools with the conditions that select them. Nothing about when-to-use is left to inference.

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?