Skip to main content
Glama
Sign In

Ménage Parfait

by fr.menageparfait
OverviewDiscussionsAdmin

Exact price for a home cleaning

get_quote
Read-onlyIdempotent

Exact price (same calculation as menageparfait.fr): TTC (show this to the customer), HT, VAT, and the cost after the 50% tax credit if the customer is eligible.

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD (today adds a same-day surcharge)
extrasNoExtras from get_services. Ask the customer before quoting a first cleaning: most add at least one (inside the oven id 11, inside the fridge id 10, windows id 15 with quantity, changing sheets id 12; move-out: Fin de bail id 18). e.g. [{"id":11},{"id":15,"quantity":4}]
bedroomsYesNumber of bedrooms (studio = 1)
bathroomsNo
conditionYesASK the customer, never assume: when the home last had a thorough (professional) clean. recent (<1 month), one_to_six_months, over_six_months (or never). First cleanings are rarely recent.
frequencyNoonce, weekly, biweekly (every 2 weeks) or monthly — recurring plans get a discountonce
surface_m2NoLiving area in m² (optional, improves accuracy)
high_ceilingsNoHaussmann building / ceilings over 3 m
furnished_occupiedNoHome is furnished and lived in

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / condition / default
      Removed value: -"recent"
    • changedInput schema / properties / condition / description
      Previous value: -"When the home last had a thorough clean: recent (<1 month), one_to_six_months, over_six_months (or never)"New value: +"ASK the customer, never assume: when the home last had a thorough (professional) clean. recent (<1 month), one_to_six_months, over_six_months (or never). First cleanings are rarely recent."
    • changedInput schema / properties / extras / description
      Previous value: -"Optional extras from get_services, e.g. [{\"id\":11},{\"id\":15,\"quantity\":4}]"New value: +"Extras from get_services. Ask the customer before quoting a first cleaning: most add at least one (inside the oven id 11, inside the fridge id 10, windows id 15 with quantity, changing sheets id 12; move-out: Fin de bail id 18). e.g. [{\"id\":11},{\"id\":15,\"quantity\":4}]"
    • changedInput schema / required
      Previous value: -[
-  "bedrooms"
-]New value: +[
+  "bedrooms",
+  "condition"
+]
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful context by naming the calculation source, listing the returned price components, and noting customer-facing use, but it does not disclose edge cases such as tax-credit eligibility conditions or same-day surcharge behavior beyond what the schema already says.

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 a single compact sentence that front-loads the core purpose and then lists the returned components. There is no filler or repetition.

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?

There is no output schema, so the description usefully lists the key returned values: TTC, HT, VAT, and the after-tax-credit cost. It is nearly complete for a quote tool, though it could specify output structure or eligibility conditions for the tax credit.

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 high at 89%, so the schema already carries most parameter meaning, including the detailed extras guidance and condition prompt. The description itself adds no parameter-specific semantics, so the baseline of 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 description clearly states that this tool returns an exact cleaning price, with TTC, HT, VAT, and post-tax-credit amounts. It is specific about the resource and output, but it does not explicitly distinguish this tool from siblings like get_post_construction_estimate or request_office_quote.

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?

The description only says to show the TTC amount to the customer; it gives no when-to-use guidance, no exclusions, and no comparison to alternative quote or estimate tools. An agent must infer the selection criteria from the tool name and sibling names.

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

All Ménage Parfait toolsInspect
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