FreeDailyPro Business Documents

business_eviction_notice_draft

Read-onlyIdempotent

Eviction notice draft

Input Schema

Name	Required	Description
`date`	Yes
`days`	Yes	Days the tenant has to leave (or to fix the problem).
`reason`	No	Default end-of-term.
`tenant`	Yes
`address`	Yes
`landlord`	Yes
`allowCure`	No	The tenant may stay by fixing the problem in time. Default true for nonpayment and lease-violation.
`violation`	No
`amountOwed`	No
`governingLaw`	No	Whose law governs, for example "the State of Texas" or "England and Wales". Default: the place where the property or the parties are.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 3, 2026

addedInput schema / properties / allowCure

Added value: +{
+  "description": "The tenant may stay by fixing the problem in time. Default true for nonpayment and lease-violation.",
+  "type": "boolean"
+}

addedInput schema / properties / amountOwed
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / days / description

Added value: +"Days the tenant has to leave (or to fix the problem)."

addedInput schema / properties / governingLaw

Added value: +{
+  "description": "Whose law governs, for example \"the State of Texas\" or \"England and Wales\". Default: the place where the property or the parties are.",
+  "maxLength": 120,
+  "type": "string"
+}

addedInput schema / properties / reason

Added value: +{
+  "description": "Default end-of-term.",
+  "enum": [
+    "nonpayment",
+    "lease-violation",
+    "end-of-term",
+    "no-cause"
+  ],
+  "type": "string"
+}

addedInput schema / properties / violation
```
Added value: +{
+  "type": "string"
+}
```

Changed5 schema fields changedNov 1, 2026
- addedInput schema / properties / address / minLength
```
Added value: +1
```
- addedInput schema / properties / date / minLength
```
Added value: +1
```
- addedInput schema / properties / days / minimum
```
Added value: +0
```
- addedInput schema / properties / landlord / minLength
```
Added value: +1
```
- addedInput schema / properties / tenant / minLength
```
Added value: +1
```
First observedOct 24, 2026

TDQS

D1.8/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered without the description. The description adds nothing beyond those structured hints — no note that it generates text rather than filing anything, no mention of jurisdictional caveats, and no statement that missing optional fields (reason, allowCure, governingLaw) fall back to defaults.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but short because it is under-specified rather than because it is efficient. There is no front-loaded verb, no structure, and no information an agent can act on.

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

Completeness1/5

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

For a 10-parameter legal-document generator with no output schema and partial schema coverage, the definition provides essentially no context about inputs, defaults, or the shape of the produced notice. It is completely inadequate for the tool's complexity.

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

Parameters1/5

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

The tool takes 10 parameters with only 40% schema description coverage, so the description is expected to compensate for undocumented inputs such as violation, amountOwed, address, landlord, and tenant. Instead it says nothing about any parameter, leaving well over half the inputs meaningless to an agent that only reads the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description "Eviction notice draft" merely restates the tool name and title in slightly different casing. It names the artifact but gives no verb, no scope, and no differentiation from sibling document-drafting tools like business_lease_draft or business_promissory_note_draft.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool, no prerequisites, and no mention of alternatives among the many business_* drafting siblings. The agent must infer everything from the name alone.

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

All FreeDailyPro Business Documents 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?