Skip to main content
Glama

Coline

Set working hours

set_working_hours
DestructiveIdempotent

Replaces the person's weekly working hours and dated time off. Read them first; this replaces all of them.

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": {
      "workspace": "<workspace>",
      "timeZone": "<timeZone>",
      "rules": "<rules>",
      "overrides": "<overrides>"
    },
    "name": "set_working_hours"
  }
}

Input Schema

NameRequiredDescriptionDefault
rulesYes
timeZoneYes
overridesYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
rulesYes
timeZoneYes
overridesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description earns credit for specifying what gets destroyed: the entire weekly pattern plus all dated time off, not a merge or patch. It still omits consequences of the call, such as what empty arrays do (clear everything?) or whether downstream scheduling/booking behavior is affected.

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?

Two short sentences, front-loaded with the destructive scope and followed by the required precondition. Nothing is wasted, though the second sentence could more explicitly tie "read them first" to a tool name.

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

Completeness4/5

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

For a fully-required, four-parameter destructive mutation with an output schema covering return values, the description does the essential job: it flags total replacement and the read-before-write step. The remaining gap is parameter-level detail around exhaustive arrays and timeZone applicability, which the sparse schema leaves unaddressed.

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 only 25% (essentially just workspace, dayOfWeek, and startMinute), so parameters rely partly on the description. "This replaces all of them" implies rules and overrides must be supplied as complete, exhaustive lists rather than deltas, which is the most important semantic here, but the description never explains the rules-vs-overrides split, the kind/disposition enums, or the role of timeZone.

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?

States a specific verb ("Replaces") plus the resources it owns (weekly working hours and dated time off), and clarifies the replacement is total rather than incremental. It signals a read-first counterpart ("Read them first") but doesn't name get_working_hours, so the sibling mapping is left implicit.

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?

Gives a concrete prerequisite: read the existing hours before calling, because the call wipes them. It does not state exclusions or name the read tool explicitly, but the sequencing guidance is unambiguous enough to act on.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources