Skip to main content
Glama

public-tools

by com.faireplace

Creer un brouillon de bail (a finaliser et signer)

create_lease_draft

Create a French residential lease draft (bail / contrat de location) from the provided info, and return a link to finalize, adjust and E-SIGN it (advanced eIDAS signature, legally binding) on FairePlace. Use whenever a user wants to create, draft or generate a lease / rental contract. Link valid 30 minutes. FR: creer / rediger / generer un bail de location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leaseYesLes conditions du bail. Ex : { rent_amount, charges_amount, deposit_amount, start_date, lease_type }.
ownerYesLe bailleur (proprietaire). Ex : { last_name, first_name, email }. Personne morale : { legal_name, email }.
logementYesLe logement. Ex : { name, address, postal_code, city, surface_area, room_count, is_furnished }.

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It reveals the link's 30-minute validity and the eIDAS signature feature, which is helpful. However, it does not describe side effects, lasting state changes, or error conditions, so some transparency gaps remain.

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

Conciseness5/5

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

The description is three sentences long, front-loaded with the core action, and includes a French usage hint for multilingual relevance. Every sentence adds value without redundancy.

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?

Given the nested parameter structure and lack of output schema, the description covers the primary output (a signable link) and the 30-minute expiration. It sets expectations for legal binding via eIDAS. Missing details like authentication requirements or post-expiry behavior, but it is sufficiently complete for a creation tool.

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?

The input schema already has 100% coverage with descriptions and examples for all three parameters. The description does not add parameter-specific details, but the schema supplies sufficient meaning. Therefore, the baseline 3 applies.

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?

The description clearly states the tool's function: 'Create a French residential lease draft... and return a link to finalize, adjust and E-SIGN it.' This distinguishes it from sibling generation tools like generate_avenant or generate_conge by specifying 'lease / rental contract' and the e-signature element.

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 explicitly says 'Use whenever a user wants to create, draft or generate a lease / rental contract.' This provides clear usage context. It does not list exclusions or alternatives, but the sibling names imply other document types.

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

All public-tools toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools are clearly distinct document generators or calculators, but check_rent_control and get_reference_rent both deal with rent control and could be confused, as could simulate_irl and simulate_irl_by_quarters. Descriptions mostly clarify boundaries, so only minor ambiguity exists.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (e.g., generate_quittance, check_address_risks, simulate_irl). The verbs vary by action but the structure is uniform and predictable across the entire set.

Tool Count4/5

With 21 tools covering a broad but focused domain of French rental law, the count is slightly above the ideal 3-15 range but each tool serves a distinct legal or calculation purpose. The scope is large but justified for a comprehensive rental toolkit.

Completeness5/5

The toolset covers the full lifecycle of a French residential lease: creation, amendments, termination, deposits, guarantors, inventories, rent receipts, unpaid rent, rent control, and rent revision. There are no obvious missing operations for the stated purpose.

Resources