Skip to main content
Glama
Sign In

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Set activity hours

set_activity_hours

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_activity_hours"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoWhen sending stops each active day, 24-hour 'HH:MM', at least an hour after start on the same day.
startNoWhen sending starts each active day, 24-hour 'HH:MM'.
timezoneNoIANA timezone name the hours are in, like 'America/New_York'.
active_daysNoThe weekdays outreach runs on; an empty list pauses all outreach.
on_behalf_ofNoA 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description goes further by disclosing partial-update semantics ('only what you pass changes') and the consequence of a bad choice (midnight sends look automated). It also documents the return payload (open_now, window_start, window_end, active_days, timezone), which fills the missing output schema.

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 summary followed by scoping rule, then a concrete fallback behavior — a logical order. Slightly long, and the closing justification about night-time sends could be trimmed, but every sentence carries usable instruction.

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?

A five-parameter mutation tool with no output schema is fully covered: partial-update semantics, scoping/impersonation, return fields, and the ambiguous-request fallback are all stated. An agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is already 100%, but the description adds real meaning the schema lacks: null/omitted parameters mean 'keep the stored value' rather than clearing a field. The on_behalf_of account-scoping concept is also reinforced in prose, tying it to the agency-client lookup tool.

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 — change the user's outreach activity hours, defined concretely as 'when Sliq sends their LinkedIn and email outreach.' It also draws an explicit boundary against a nearby concept (the user's own working hours), so the agent knows exactly which setting is being mutated.

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?

Explicitly routes the agent: working hours go to memory unless the user asks for outreach in those hours, and for vague requests like 'after hours too' it prescribes proposing a start/end and confirming rather than opening the whole day. It also names list_agency_clients as the source for on_behalf_of values.

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

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