maideo

get_quote

Obtain a firm price quote for professional home cleaning services in France. Generate a quote valid for 72 hours to proceed with booking creation.

Instructions

Get a firm price quote for a cleaning booking. Returns a quoteToken valid for 72h that must be passed to create_booking.

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": {
      "zip": "<zip>",
      "nbHeuresSemaine": "<nbHeuresSemaine>",
      "frequency": "<frequency>"
    },
    "name": "get_quote"
  }
}

Input Schema

Name	Required	Description	Default
`zip`	Yes
`city`	No
`nbHeuresSemaine`	Yes	Number of hours per intervention
`nbPrestaSemaine`	No	Number of interventions per week
`frequency`	Yes
`prestation`	No		MENAGE
`prestationInfo`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Apr 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and does well by disclosing key behavioral traits: it returns a quoteToken valid for 72 hours that must be passed to create_booking. This adds valuable context about output format, validity, and dependencies, though it could mention error handling or rate limits.

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 front-loaded and concise with two sentences that efficiently convey purpose and output behavior. Every sentence earns its place by adding critical information without redundancy or fluff.

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 complexity (7 parameters, nested objects) and no annotations or output schema, the description is reasonably complete for a quote tool. It covers purpose, output usage, and validity, but could improve by hinting at parameter roles or error cases to fully guide the agent.

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 low at 29%, but the description doesn't add any parameter-specific information beyond what the schema provides. It implies parameters relate to booking details but doesn't explain semantics like zip vs. city or prestationInfo. Baseline is 3 as the schema does some work, but the description doesn't compensate for the coverage gap.

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 purpose with a specific verb ('Get') and resource ('firm price quote for a cleaning booking'), and it distinguishes from siblings by mentioning the output is used by create_booking. It goes beyond just restating the name to explain the functional outcome.

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 provides clear context by stating the quote is used for create_booking, implying this tool should be called before that sibling. However, it doesn't explicitly mention when not to use it or alternatives like search_coverage, which could help in decision-making.

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

Deploy Server