DouxProcess Directory

Get quotes from contractors nearby

request_quotes

Sends the person's request to up to 3 licensed contractors near them who use Luma (the contractor app DouxProcess Inc. builds), Luma Pro members first, and returns the other matches with their own contact details. Call it once without consent to get consent_text and the disclosure, show both to the person, and call again with consent=true only if they agree. Never include card numbers, ID numbers or passwords.

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": {
      "category": "<category>",
      "where": "<where>",
      "name": "<name>",
      "details": "<details>",
      "consent": "<consent>"
    },
    "name": "request_quotes"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	The person's name.
`email`	No	Or an email address.
`phone`	No	A phone number the businesses can reply to.
`where`	Yes	A city and state ('Pasadena, CA') or a 5-digit ZIP. Never the person's own street address.
`address`	No	Optional: the job address, only if the person gave it for this request.
`consent`	Yes	True only if the person read and agreed to consent_text.
`details`	Yes	What they need, in their words. No card numbers, ID numbers or passwords.
`category`	Yes	A category id from list_categories, e.g. roofer.
`preferred_times`	No	Optional: when they are free.

Output Schema

Name	Required	Description	Default
`why`	No
`next`	No
`sent`	Yes
`count`	No
`others`	No
`sent_to`	No
`disclosure`	No
`consent_text`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true. The description adds real behavioral context beyond them: an outbound message is sent to at most 3 contractors, Luma Pro members are prioritized, non-sent matches are returned with contact details, and there is a two-call consent gate. It omits failure modes or what happens if no matches exist.

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?

Three compact sentences, front-loaded with the core action and ranking, followed by the consent workflow and the PII rule. Each sentence earns its place, though the parenthetical appositive about the contractor app is slightly expendable.

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?

An output schema exists, so return values need not be explained. The consent sequencing and PII constraints are covered. What's left thin is behavior when fewer than 3 or zero contractors match, but that is minor for this tool's complexity.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description nevertheless adds genuine meaning to the consent parameter by explaining the consent_text/disclosure round-trip and when consent=true is permissible, plus a PII restriction on details. That is value beyond the schema text.

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?

Specific verb and resource: sends the person's request to up to 3 licensed contractors nearby who use Luma, and returns the other matches with contact details. This is clearly distinguishable from siblings like find_businesses (search), request_contact, and request_service.

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?

Explicit procedure: call once without consent to obtain consent_text and the disclosure, show both, then call again with consent=true only if the person agrees. It doesn't name or rule out sibling alternatives (e.g. request_service vs request_contact), so it falls short of a 5.

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

All DouxProcess Directory 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?