DouxProcess Directory

Request a quote

request_service

Read-onlyIdempotent

Open the request form for one business the person chose (ChatGPT local services Get Quote). The form shows the consent sentence and sends only when the person ticks it. For a business that does not take requests it shows the business's own phone and website.

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": {
      "business_id": "<business_id>"
    },
    "name": "request_service"
  }
}

Input Schema

Name	Required	Description	Default
`business_id`	Yes	The business id (its slug) from find_businesses or the business feed.

Output Schema

Name	Required	Description	Default
`how`	No
`business`	Yes
`can_request`	Yes
`consent_text`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / business / properties / luma

Added value: +{
+  "properties": {
+    "books_online": {
+      "type": "boolean"
+    },
+    "site": {
+      "type": "string"
+    },
+    "site_url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 24, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, and the description is consistent with that (it opens a form rather than sending). It adds genuine context: the consent sentence, that sending requires the person to tick a box, and the degraded behavior showing the business's own phone/website when requests aren't accepted.

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?

Two tightly written sentences with the primary action front-loaded and the fallback behavior following. No filler, though the parenthetical product label is slightly noisy.

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 needn't be explained. For a one-parameter tool with full annotation coverage, the description covers the main flow and the non-request fallback; only the explicit sibling routing is missing.

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 coverage is 100% and the single business_id parameter is fully documented in the schema, so the baseline is 3. The description only adds that the id comes from a person-chosen business, which is already implied by 'business feed' in the schema.

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?

States a specific verb (open the request form) and resource (one business chosen), and the phrasing 'one business' implicitly distinguishes it from the plural sibling request_quotes. Clear enough that an agent knows exactly what action results.

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

Usage Guidelines3/5

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

The 'for one business the person chose' constraint implies the when-to-use case, and it explains the fallback path (phone/website) for businesses that don't accept requests. However, it never explicitly contrasts with request_quotes, request_contact, or ask, so the agent must infer the boundary itself.

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?