Field Service Business Platform by Doing Work

homeowner_sendRequest

Send your request to shops on Doing Work that serve the address and do the trade. Needs at least one photo. Show the customer homeowner.previewShops first and pass any shops they removed in exclude_shop_ids. Shops reply in their own time; check with homeowner.getRequest.

Input Schema

Name	Required	Description	Default
`request_id`	Yes
`exclude_shop_ids`	No	Optional. Shops from homeowner.previewShops the customer removed. They do not get the request.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

addedInput schema / properties / exclude_shop_ids

Added value: +{
+  "description": "Optional. Shops from homeowner.previewShops the customer removed. They do not get the request.",
+  "items": {
+    "format": "uuid",
+    "type": "string"
+  },
+  "maxItems": 100,
+  "type": "array",
+  "uniqueItems": true
+}

changedOutput schema / anyOf

Previous value: -[
-  {
-    "properties": {
-      "deleted_after": {
-        "type": "string"
-      },
-      "finding_shops": {
-        "type": "boolean"
-      },
-      "next": {
-        "type": "string"
-      },
-      "pledge": {
-        "type": "string"
-      },
-      "prices": {
-        "type": "string"
-      },
-      "request_id": {
-        "format": "uuid",
-        "type": "string"
-      },
-      "sent_to_shops": {
-        "type": "integer"
-      },
-      "status": {
-        "type": "string"
-      },
-      "stripe_fee": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "request_id",
-      "status",
-      "sent_to_shops",
-      "finding_shops",
-      "next",
-      "deleted_after",
-      "pledge",
-      "stripe_fee",
-      "prices"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "approval_id": {
-        "format": "uuid",
-        "type": "string"
-      },
-      "approval_required": {
-        "enum": [
-          true
-        ],
-        "type": "boolean"
-      },
-      "expires_at": {
-        "format": "date-time",
-        "type": "string"
-      },
-      "message": {
-        "type": "string"
-      },
-      "status": {
-        "enum": [
-          "pending"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "approval_required",
-      "approval_id",
-      "status",
-      "expires_at",
-      "message"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "deleted_after": {
+        "type": "string"
+      },
+      "excluded_shops": {
+        "type": "integer"
+      },
+      "finding_shops": {
+        "type": "boolean"
+      },
+      "next": {
+        "type": "string"
+      },
+      "pledge": {
+        "type": "string"
+      },
+      "prices": {
+        "type": "string"
+      },
+      "request_id": {
+        "format": "uuid",
+        "type": "string"
+      },
+      "sent_to_shops": {
+        "type": "integer"
+      },
+      "status": {
+        "type": "string"
+      },
+      "stripe_fee": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "request_id",
+      "status",
+      "sent_to_shops",
+      "excluded_shops",
+      "finding_shops",
+      "next",
+      "deleted_after",
+      "pledge",
+      "stripe_fee",
+      "prices"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "approval_id": {
+        "format": "uuid",
+        "type": "string"
+      },
+      "approval_required": {
+        "enum": [
+          true
+        ],
+        "type": "boolean"
+      },
+      "expires_at": {
+        "format": "date-time",
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "status": {
+        "enum": [
+          "pending"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "approval_required",
+      "approval_id",
+      "status",
+      "expires_at",
+      "message"
+    ],
+    "type": "object"
+  }
+]

First observedNov 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does disclose key traits: a hard photo prerequisite, shop filtering by address/trade, and asynchronous replies requiring polling via homeowner.getRequest. It does not explain whether it creates or dispatches an existing request, what happens on failure, or whether it can be re-sent, leaving some mutation semantics unstated.

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 short sentences, front-loaded with the action, then prerequisites, then follow-up; almost no filler. The opening clause 'on Doing Work' is a slightly opaque product reference but does not waste much space.

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 two-parameter mutation with an output schema (so return values need not be described), the definition covers prerequisites, sequencing, and the async outcome path. The remaining gap is the origin/semantics of the required request_id and any permission or failure conditions.

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 50%: exclude_shop_ids is already documented in the schema, and the description only restates its intent slightly more concretely (shops the customer removed do not get the request). The required request_id has no description in either place, and the description never says where it comes from (presumably homeowner.createRequest).

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 and resource ('Send your request to shops') plus the targeting scope ('that serve the address and do the trade'). It also names the sibling tools it interacts with (homeowner.previewShops, homeowner.getRequest), so an agent can place it in the workflow without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite sequence: show the customer homeowner.previewShops first, pass removed shops via exclude_shop_ids, and requires at least one photo. It also names the follow-up path (check homeowner.getRequest) since replies are asynchronous.

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

All Field Service Business Platform by Doing Work 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?