SalesHookAI

Clock out

clockOut

Stops the current live time clock (Stempeluhr) and books the elapsed time as a time entry — clock out / punch out / Feierabend.

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": "clockOut"
  }
}

Input Schema

Name	Required	Description
`note`	No	Optional note appended to the booked entry
`end_time`	No	When work really ended, as YYYY-MM-DDTHH:mm German local time. Use when the timer was forgotten.
`keep_current_time`	No	Only when the user confirms a very long timer really ended now.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already flag a non-read-only, non-destructive write, and the description adds the crucial consequence: elapsed time is booked as a time entry. It does not cover failure modes (no active timer) or the double-invocation case despite idempotentHint=false.

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?

A single front-loaded sentence stating the action and its side effect, with the synonymous terms (punch out / Feierabend) tacked on for matching. Nothing is wasted.

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 zero-required-parameter action tool with full schema coverage and annotations, the definition conveys the core effect and enough context to call it. Minor gaps remain around what happens when no timer is running and how the booked entry is attributed.

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% and each parameter already carries its own explanation, including the correction and confirmation cases. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 and resource: it stops the running time clock (Stempeluhr) and books the elapsed time as a time entry. The counterpart to clockIn is implied by 'current live,' so an agent can tell the pair apart, though clockIn is not named explicitly.

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 rather than stated: it applies while a timer is live, and the schema hints end_time is for forgotten timers. There is no explicit when-not guidance (e.g., while on a break vs. endBreak) and no named alternative tool.

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

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