AskRentAI

Get Work Orders

get_work_orders

Read-onlyIdempotent

Service Manager work orders / maintenance issues across EVERY category.

The general maintenance board (not just resident complaints — use get_resident_concerns for those). Pulls /ServiceManagerIssues directly with category, status, priority, open/close dates, property/unit, and detail. Set open_only=False to include closed orders and an average open→close turnaround stat. Filter by property, category, status, priority, or an opened-date window. Answers: 'what work orders are open', 'maintenance turnaround at ', 'show closed work orders this month'.

``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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_work_orders"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`status`	No
`category`	No
`end_date`	No
`location`	No
`priority`	No
`property`	No
`open_only`	No
`start_date`	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 carry readOnly/idempotent/openWorld/non-destructive, and the description adds real behavioral context beyond them: open_only=False also returns an average open→close turnaround stat, output is labelled per Location, unreachable Locations are reported as skipped, and filtering by a Location-scoped ID requires passing that Location. It stops short of describing pagination/limit behavior, so not 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?

Front-loaded with purpose and the sibling exclusion, then the ranged behaviors, then the location note. Dense but nearly every clause carries information; the location paragraph is slightly long-winded relative to the rest.

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 shape need not be explained, and the description covers scoping, filtering, the closed-order mode switch, and multi-Location semantics. The main remaining hole is what `limit` does and how results are truncated/ordered.

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 coverage the description must carry all nine parameters, and it covers most of them: the location parameter gets a detailed spec (single ID, comma-separated list, "all", blank default semantics), plus category, status, priority, property, and the start/end opened-date window. Only `limit` is left unexplained.

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 resource (Service Manager work orders / maintenance issues) and the exact source endpoint (/ServiceManagerIssues), and explicitly distinguishes itself from the sibling get_resident_concerns. An agent can tell immediately what this returns and what it is not.

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?

Names the alternative (get_resident_concerns) and the condition that selects it, explains that open_only=False is required to see closed orders, and gives three concrete question phrasings it answers. Usage is fully determined.

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?