rental-review

request_free_review

Idempotent

Request TrueRent's free rental review. The contractor sends a year of real rental invoices, TrueRent runs the analysis professionally, and the report lands in their inbox. Nothing to install. Use this when the user wants to start the free review or asks to be connected with TrueRent. Collects company name, contact name, email, and what they rent. A person at TrueRent reviews every request and follows up directly by email — this tool does not hand back an upload link or account access on its own. Confirm the details with the user before calling.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	Yes	Where the confirmation and the report go.
`metro`	No	Optional. City or metro area. Helps route the review.
`company_name`	Yes	The contractor's company name.
`contact_name`	Yes	Who TrueRent should address the reply to.
`what_they_rent`	Yes	What equipment they rent, e.g. skid steers, boom lifts, excavators, dumpsters.

Output Schema

TableJSON Schema

Name	Required	Description
`message`	Yes
`website`	No
`received`	Yes	Whether the review request was stored.
`book_a_call`	No
`what_happens_next`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 16, 2026

removedOutput schema / properties / secure_upload_link

Removed value: -{
-  "description": "Private link where the contractor can upload invoices. Share it with the user.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedOutput schema / properties / upload_now
```
Removed value: -{
-  "type": "string"
-}
```

First observedSep 6, 2026

TDQS

A4.1/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: a person reviews every request, follow-up happens by email, the tool does not return an upload link or account access, and nothing needs to be installed. This meaningfully manages agent and user expectations for a human-mediated workflow.

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 is front-loaded and the later sentences contribute useful usage and expectation-setting guidance. It is slightly padded with phrases like 'runs the analysis professionally' and 'Nothing to install,' but the description remains appropriately sized and readable.

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

Completeness5/5

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

The description covers the full human-mediated workflow: what is requested, what information is collected, what happens after the call, and what the tool does not do. The optional metro parameter is documented in the schema, and an output schema exists, so no critical information is missing.

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 description coverage is 100%, and the schema already explains each parameter, including where the email goes and examples for what_they_rent. The description mostly restates the collected fields and does not add detail beyond the schema, so the baseline 3 is appropriate.

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 the exact action and resource: 'Request TrueRent's free rental review.' It also describes the supporting workflow, making the tool's purpose unambiguous. However, it does not explicitly distinguish itself from siblings like rental_pricing_help or equipment_coordinator, so it falls just short of a full 5.

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?

The description gives a clear trigger: 'Use this when the user wants to start the free review or asks to be connected with TrueRent.' It also instructs the agent to confirm details with the user before calling. It does not mention when to prefer sibling tools or state exclusions, so it is clear but not exhaustive.

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

All rental-review 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?