Detritus Site Services: Get a Quote

Check service availability

get_service_availability

Read-onlyIdempotent

Check whether Detritus serves a US ZIP code and list the dumpster sizes, portable sanitation products, disposal materials, and other jobsite services (temporary fencing, storage containers, water, power) available there. 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": {
      "zip": "<zip>"
    },
    "name": "get_service_availability"
  }
}

Input Schema

Name	Required	Description	Default
`zip`	Yes	Delivery ZIP code (5 digits, optional +4).

Output Schema

Name	Required	Description
`zip`	Yes
`reason`	No
`message`	No
`products`	No
`available`	Yes
`siteServices`	No	Other jobsite services (fencing, storage, water, power) to include on the same request.
`dumpsterSizes`	No
`disposalMaterials`	No
`dumpsterRentalTypes`	No	Allowed rentalType values for dumpster-only jobs.
`portaPottyRentalTypes`	No	Allowed rentalType values for porta-potty or mixed jobs.

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedOct 23, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / disposalMaterials / items / $ref
```
Removed value: -"#/properties/dumpsterSizes/items"
```
- addedOutput schema / properties / disposalMaterials / items / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / disposalMaterials / items / properties
```
Added value: +{
+  "id": {
+    "type": "string"
+  },
+  "label": {
+    "type": "string"
+  }
+}
```
- addedOutput schema / properties / disposalMaterials / items / required
```
Added value: +[
+  "id"
+]
```
- addedOutput schema / properties / disposalMaterials / items / type
```
Added value: +"object"
```
- removedOutput schema / properties / products / items / $ref
```
Removed value: -"#/properties/dumpsterSizes/items"
```
- addedOutput schema / properties / products / items / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / products / items / properties
```
Added value: +{
+  "id": {
+    "type": "string"
+  },
+  "label": {
+    "type": "string"
+  }
+}
```
- addedOutput schema / properties / products / items / required
```
Added value: +[
+  "id"
+]
```
- addedOutput schema / properties / products / items / type
```
Added value: +"object"
```
- removedOutput schema / properties / siteServices / items / $ref
```
Removed value: -"#/properties/dumpsterSizes/items"
```
- addedOutput schema / properties / siteServices / items / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / siteServices / items / properties
```
Added value: +{
+  "id": {
+    "type": "string"
+  },
+  "label": {
+    "type": "string"
+  }
+}
```
- addedOutput schema / properties / siteServices / items / required
```
Added value: +[
+  "id"
+]
```
- addedOutput schema / properties / siteServices / items / type
```
Added value: +"object"
```
First observedOct 19, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, and the trailing 'Read-only.' merely restates them. The description does add the useful scope fact that coverage is US-only, but it doesn't say whether an unserved ZIP returns an empty result or an error, which is the one behavioral detail an agent would actually want.

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 sentences, zero filler, with the core capability front-loaded and the safety note last. Every clause carries information about scope or coverage.

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?

For a one-parameter read tool with full annotations and an output schema, the description covers purpose, domain (US ZIP), and the categories returned. The only real gap is the semantics of a negative result, which is not clearly covered elsewhere.

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?

There is a single parameter with 100% schema coverage, including a regex pattern and format note, so the schema does the heavy lifting. The description adds one meaningful clarification — that the ZIP is a US ZIP — but nothing about the optional +4 suffix or validation behavior.

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 gives a concrete verb (check) and resource (Detritus service availability) and enumerates what the response covers — dumpster sizes, sanitation products, disposal materials, and other jobsite services. That clearly separates it from request/quote siblings, but it never names an alternative explicitly, so it falls just short of a 5.

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?

Nothing states when to call this versus check_service_request_status, get_quote, or make_service_request, nor that it should precede a service request. Usage is only implied by the notion of a ZIP-code coverage lookup, which is close to self-evident but never spelled out.

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?