Detritus Site Services: Get a Quote

Get quote

get_quote

Read-onlyIdempotent

Get the customer-facing quote for an existing Detritus request: totals, price breakdown by product type, and quote link. Requires serviceRequestId and the phone or email used on the request. Returns customer pricing only (no vendor cost). Read-only.

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": {
      "serviceRequestId": "<serviceRequestId>"
    },
    "name": "get_quote"
  }
}

Input Schema

Name	Required	Description
`email`	No	Email used on the service request.
`phone`	No	Phone used on the service request (preferred if ≥10 digits).
`serviceRequestId`	Yes	Id returned by make_service_request.

Output Schema

Name	Required	Description	Default
`quote`	No
`status`	Yes
`message`	Yes
`keepPolling`	Yes
`serviceRequestId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 23, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / email / pattern

Added value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"

changedOutput schema / properties / quote / properties / quoteNumber / anyOf

Previous value: -[
-  {
-    "minLength": 0,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "",
+    "minLength": 0,
+    "type": "string"
+  },
+  {
+    "description": "",
+    "type": "null"
+  }
+]

changedOutput schema / properties / quote / properties / quoteUrl / anyOf

Previous value: -[
-  {
-    "minLength": 0,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "",
+    "minLength": 0,
+    "type": "string"
+  },
+  {
+    "description": "",
+    "type": "null"
+  }
+]

changedOutput schema / properties / quote / properties / total / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "",
+    "type": "number"
+  },
+  {
+    "description": "",
+    "type": "null"
+  }
+]

First observedOct 19, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the redundant 'Read-only' is not the main contribution. The description adds genuinely useful behavior: access requires identity verification via the phone/email on the request, and the response is deliberately limited to customer pricing with vendor cost excluded.

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?

Two dense sentences with no filler; the resource and returned contents come first, followed by prerequisites and scope limits. Every clause carries information an agent would need.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema handling return shape and annotations covering safety, the description fills the remaining gaps: what data is returned, the identity verification requirement, and the deliberate exclusion of vendor cost. Nothing needed to call it correctly is missing.

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, but the description adds meaning the schema does not: while only serviceRequestId is required in schema, the text indicates the caller also needs the email or phone on file. That clarifies how the identifier parameters are actually used for authorization.

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?

States a specific verb (get) and resource (the customer-facing quote) and enumerates exactly what comes back: totals, price breakdown by product type, and quote link. It also scopes the object to an existing Detritus service request, which separates it from make_service_request and check_service_request_status.

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?

It gives prerequisites (serviceRequestId plus phone or email used on the request), which implies this is a lookup on an already-created request. However, it never explicitly says when to prefer this over check_service_request_status or what to do if the quote isn't ready, leaving usage to inference.

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

All Detritus Site Services: Get a Quote 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?