Duty & Rest for agents

duty_record_event

Record a duty event for one of your agents (kinds: compaction, verification_failure, model_switch, tool_error, work_hour, session_restart).

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": {
      "agent": "<agent>",
      "kind": "<kind>"
    },
    "name": "duty_record_event"
  }
}

Input Schema

Name	Required	Description	Default
`ts`	No
`kind`	Yes
`agent`	Yes
`hours`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

B3/5.0

Behavior2/5

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

There are no annotations provided, and the description is purely functional, giving zero insight into how the tool behaves, such as required permissions, success/failure responses, or how 'ts' and 'hours' are validated.

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?

The definition is highly concise. It provides only necessary information—the list of valid events—without any superfluous phrasing.

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

Completeness2/5

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

Although it defines the list of valid event types, the tool is incomplete for an agent as it fails to define the meaning, format, or constraints of the remaining three parameters ('agent', 'ts', 'hours').

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?

With a schema coverage of 0%, the description must define all parameters. It only provides semantic value for the 'kind' field by listing valid enumerations. The semantics of 'agent', 'ts', and 'hours' are completely undocumented.

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 clearly states the action ('Record a duty event') and provides a precise list of acceptable event 'kinds'. It achieves good clarity on what the tool captures.

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?

Usage is implied by the list of event 'kinds' (e.g., use this when a 'verification_failure' occurs). However, it does not provide explicit guidance on when to use this tool versus its siblings like 'duty_check'.

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

All Duty & Rest for agents 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?