RedFlagLease

Scan a lease for red flags

check_lease

Scan a US residential lease for risky, unusual or likely unenforceable clauses under that state's tenant law. Pass the full lease text. Returns every flagged clause with its severity, the risk and the state rule/citation, plus a link to the full report on redflaglease.com (quoted clauses, how to fix each one, missing protections, questions to ask, ready-to-send negotiation email, printable and emailed). Takes up to ~45 seconds. Information, not legal advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>",
      "lease_text": "<lease_text>"
    },
    "name": "check_lease"
  }
}

Input Schema

Name	Required	Description	Default
`state`	Yes	Two-letter US state code, e.g. CA, NY, TX
`lease_text`	Yes	Full text of the lease (at least a few paragraphs)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations cover the safety profile (destructiveHint=false, openWorldHint=true), and the description adds genuinely useful behavior beyond them: a ~45 second runtime expectation, the fact that a report is hosted externally at redflaglease.com, and a 'not legal advice' disclaimer. It does not clarify why readOnlyHint is false for what reads like a scan, which is the one behavioral loose end.

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, then input instruction, then return contents, latency and disclaimer. Three sentences with little waste; the long parenthetical enumerating report contents is slightly dense but each item is informative.

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?

No output schema exists, and the description compensates well by enumerating what comes back: every flagged clause with severity, risk, state rule/citation, plus a report link containing quoted clauses, fixes, missing protections, questions and a negotiation email. Latency, external dependency and legal disclaimer are all disclosed, so an agent has everything needed to call and interpret it.

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 coverage is 100% with only two parameters, each already documented (two-letter state code, full lease text with a minimum length). The description reinforces 'Pass the full lease text' but adds no format or constraint detail beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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?

States a specific verb and resource with clear scope: 'Scan a US residential lease for risky, unusual or likely unenforceable clauses under that state's tenant law.' The 'US residential' qualifier usefully bounds the domain, and 'Pass the full lease text' signals this is a document-scanning tool rather than a Q&A tool. It never names the sibling tenant_law, so sibling differentiation is left implicit rather than explicit.

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

Usage Guidelines3/5

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

Scope limits ('US residential lease') imply when the tool applies, and 'Pass the full lease text' implies the input mode. However, there is no explicit when-not-to-use guidance (commercial leases, non-US leases) and no routing to the tenant_law sibling for general questions. Usage is inferable but not stated.

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

All RedFlagLease 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?