Field Service Business Platform by Doing Work

reports_today

The shop's today queues in one call: visits today, visits in the next 7 days with nobody assigned, new requests, quotes and change orders waiting on the customer, overdue and draft invoices, done jobs not invoiced, time waiting for approval, approvals waiting on the owner, open tasks due by today and done visits with no quote sent yet. Each list shows the first 25 with the full count.

Input Schema

Name	Required	Description	Default
`date`	No	The day to read, in the shop's time zone. Default: today there.
`shop_id`	Yes

Output Schema

Name	Required	Description
`date`	Yes
`capacity`	Yes	F5: the next 5 working days from this day, how booked each is and how many 2 hour visits still fit.
`currency`	Yes
`time_zone`	Yes
`open_tasks`	Yes	H1: open tasks overdue or due by the end of the day, overdue first, then by job.
`quote_queue`	Yes	J6: visits done a day or more ago (last 14 days) on open jobs with no quote sent yet.
`new_requests`	Yes
`visits_today`	Yes
`draft_invoices`	Yes
`quotes_waiting`	Yes	Sent, not yet signed or declined; oldest first.
`jobs_to_invoice`	Yes	Done jobs with no invoice (voided ones do not count).
`time_to_approve`	Yes
`invoices_overdue`	Yes
`approvals_pending`	Yes
`unassigned_visits`	Yes	Scheduled visits from the start of the day through the next 7 days with nobody assigned.
`change_orders_waiting`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 3, 2026

addedOutput schema / properties / capacity

Added value: +{
+  "description": "F5: the next 5 working days from this day, how booked each is and how many 2 hour visits still fit.",
+  "properties": {
+    "days": {
+      "items": {
+        "properties": {
+          "booked_minutes": {
+            "type": "integer"
+          },
+          "date": {
+            "type": "string"
+          },
+          "fits": {
+            "type": "integer"
+          },
+          "free_minutes": {
+            "type": "integer"
+          },
+          "open_minutes": {
+            "type": "integer"
+          },
+          "percent_booked": {
+            "type": "integer"
+          },
+          "weekday": {
+            "type": "string"
+          },
+          "workers": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "date",
+          "weekday",
+          "open_minutes",
+          "booked_minutes",
+          "free_minutes",
+          "percent_booked",
+          "fits",
+          "workers"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "hours_source": {
+      "type": "string"
+    },
+    "next_actions": {
+      "description": "Useful next steps to offer, in plain words. op names the op to call, when there is one.",
+      "items": {
+        "properties": {
+          "op": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "say": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "say",
+          "op"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "time_zone": {
+      "type": "string"
+    },
+    "visit_minutes": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "time_zone",
+    "hours_source",
+    "visit_minutes",
+    "days",
+    "next_actions"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / open_tasks

Added value: +{
+  "description": "H1: open tasks overdue or due by the end of the day, overdue first, then by job.",
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "assignee_id": {
+            "format": "uuid",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "due_at": {
+            "format": "date-time",
+            "type": "string"
+          },
+          "job_id": {
+            "format": "uuid",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "job_summary": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "overdue": {
+            "type": "boolean"
+          },
+          "task_id": {
+            "format": "uuid",
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "task_id",
+          "title",
+          "job_id",
+          "job_summary",
+          "assignee_id",
+          "due_at",
+          "overdue"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "items"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / quote_queue

Added value: +{
+  "description": "J6: visits done a day or more ago (last 14 days) on open jobs with no quote sent yet.",
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "customer_name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "done_at": {
+            "format": "date-time",
+            "type": "string"
+          },
+          "job_id": {
+            "format": "uuid",
+            "type": "string"
+          },
+          "job_summary": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "visit_id": {
+            "format": "uuid",
+            "type": "string"
+          }
+        },
+        "required": [
+          "visit_id",
+          "job_id",
+          "job_summary",
+          "customer_name",
+          "done_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "items"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "date",
-  "time_zone",
-  "currency",
-  "visits_today",
-  "unassigned_visits",
-  "new_requests",
-  "quotes_waiting",
-  "change_orders_waiting",
-  "invoices_overdue",
-  "draft_invoices",
-  "jobs_to_invoice",
-  "time_to_approve",
-  "approvals_pending"
-]New value: +[
+  "date",
+  "time_zone",
+  "currency",
+  "visits_today",
+  "unassigned_visits",
+  "new_requests",
+  "quotes_waiting",
+  "change_orders_waiting",
+  "invoices_overdue",
+  "draft_invoices",
+  "jobs_to_invoice",
+  "time_to_approve",
+  "approvals_pending",
+  "open_tasks",
+  "capacity",
+  "quote_queue"
+]

First observedNov 1, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose one genuinely useful trait: each list is truncated to the first 25 with the full count shown, which prevents an agent from mistaking the result for a complete set. It says nothing about read-only semantics, permissions, time-zone handling, or cost of the multi-queue aggregation.

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?

Front-loaded with the core idea and no filler wording; the long enumeration is dense but every listed item defines scope. It would read better as a structured list than a single run-on sentence, but nothing is padding.

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

Completeness3/5

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

An output schema exists, so the enumerated queue names are arguably restating what the schema already declares, while the parts that genuinely need explanation — the date parameter beyond the default and the boundary versus reports_week — go unaddressed. 25-item truncation is the one behavioral gap it does close.

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

Parameters2/5

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

Schema coverage is 50% (date documented, shop_id bare), so the description needs to compensate but adds nothing. Worse, the description frames everything as 'today' and never acknowledges that the date parameter lets you read any day — an agent could plausibly conclude only today is readable.

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 names the resource concretely — 'the shop's today queues' — and enumerates the eleven kinds of items returned, so an agent knows exactly what data lands in the response. It lacks an explicit verb and never contrasts itself with nearby siblings such as reports_week, reports_owed, or reports_revenue, so differentiation is by inference from 'today' only.

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?

'in one call' implies this replaces several separate queries, which is a usable hint about when to reach for it. But there is no explicit when-to-use/when-not, no named alternative (reports_week is the obvious overlap and goes unmentioned), and no guidance for non-today dates even though the tool accepts a date parameter.

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?