Help by DeltaBreen

set_reply_times

Replace the workspace's working hours and reply-time targets (start from get_reply_times). A ticket then has a time to reply by whenever it waits on the team, counted in working hours, and is late once that passes. Tickets already waiting get their new time. Owner or admin; Pro and higher, with more than one set on Business.

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": {
      "timezone": "<timezone>",
      "hours": "<hours>",
      "targets": "<targets>"
    },
    "name": "set_reply_times"
  }
}

Input Schema

Name	Required	Description
`hours`	Yes	The days the team works, one entry a day. An empty list means round the clock.
`targets`	Yes	The sets of targets, the one for everyone first. This replaces the list.
`timezone`	Yes	The workspace's time zone as an IANA name, like "Europe/Dublin".

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 27, 2026
- changedInput schema / $defs / TargetMinutes / properties / high / type
```
Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"
```
- changedInput schema / $defs / TargetMinutes / properties / low / type
```
Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"
```
- changedInput schema / $defs / TargetMinutes / properties / normal / type
```
Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"
```
- changedInput schema / $defs / TargetMinutes / properties / urgent / type
```
Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"
```
First observedOct 27, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the thin annotations (readOnlyHint=false, destructiveHint=false), it discloses that this replaces rather than patches existing configuration, that in-flight tickets get recalculated deadlines, and that permissions and plan tiers gate the call. Those are exactly the side effects an agent needs before overwriting live settings.

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?

Four sentences, front-loaded with the mutation itself and the read-first hint; the permission and plan constraints are compressed into one trailing clause. Slightly dense in the eligibility sentence but nothing is wasted.

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 no output schema and minimal annotations, the description carries its weight: it covers replacement semantics, the dependency on get_reply_times, downstream effect on waiting tickets, and authorization/plan constraints. Nothing essential for a correct call 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 description coverage is 100%, so timezone/hours/targets and the nested TargetSet semantics are already documented in the schema. The description explains the domain model (working-hours counting, one set for everyone vs. conditional sets) but does not add parameter-level detail beyond that, which is the expected baseline.

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?

Opens with a specific verb+resource ('Replace the workspace's working hours and reply-time targets') and immediately names the sibling get_reply_times as the read counterpart, so an agent can distinguish it from every other set_*/get_* tool in the list.

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

Usage Guidelines4/5

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

'start from get_reply_times' establishes the required read-modify-write workflow for a full-replacement tool, and 'Owner or admin; Pro and higher, with more than one set on Business' states prerequisites up front. It stops short of explicit when-not-to-use guidance, so it falls just below a 5.

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

All Help by DeltaBreen 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?