Sliq

Set daily digest

set_daily_digest

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_daily_digest"
  }
}

Input Schema

Name	Required	Description
`on_behalf_of`	No	A teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.
`email_enabled`	No	Whether to send the daily digest by email.
`slack_enabled`	No	Whether to send the daily digest as a Slack DM; it delivers nothing until Slack is connected.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / on_behalf_of / description

Previous value: -"An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."New value: +"A teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."

AddedOct 21, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the minimal annotations (readOnly=false, destructive=false), the description discloses real behavior: only supplied fields mutate, enabling email clears a suppression from failed sends, and turning a channel off persists until the user re-enables it. It also describes the response fields, which matters because no output schema exists.

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?

The core behavior is front-loaded in the first clause, and the summary/returns split keeps side effects separate from the return shape. Slight markup overhead, but no sentence is filler.

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?

For a three-parameter, zero-required settings toggle with no output schema, the description covers mutation scope, side effects, reversibility, channel caveats, and return fields. There is little an agent would still need to know before calling it.

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%, with each of the three parameters already documented, including the on_behalf_of act-as semantics and the Slack connectivity caveat. The description adds only a general partial-update rule and never mentions on_behalf_of, so it does not meaningfully exceed the schema.

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 summary states a specific verb and resource ('Turn the user's daily digest on or off by email or by Slack') and names the two channels, so the agent knows exactly what changes. It does not name any sibling (e.g. set_reply_alerts or get_settings) for contrast, so differentiation is left to inference.

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?

'Only what you pass changes' implies a partial-update pattern, which guides invocation, and the note that email-on clears a failed-send pause tells the agent when this call has a side benefit. However, there is no explicit when-to-use, when-not-to-use, or pointer to a sibling for reading settings versus writing them.

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

All Sliq 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?