SalesHookAI

Create task

createTask

Creates a task for a team member (or the user) with a due date and optional times, project and reminder. The assigned teammate is notified in the app and by e-mail, as when a task is created in the app; nothing goes to customers.

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": {
      "title": "<title>",
      "date": "<date>"
    },
    "name": "createTask"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	Due date in YYYY-MM-DD format
`note`	No	Additional notes for the task
`title`	Yes	Task title / description
`endTime`	No	End time HH:MM (optional)
`workerId`	No	User ID of the team member (alternative to workerName)
`projectId`	No	Project ID to link the task to (optional)
`startTime`	No	Start time HH:MM (optional)
`workerName`	No	Name of the team member to assign the task to
`projectName`	No	Project name to link the task to (optional)
`reminderTime`	No	Time HH:MM on the due date to send a reminder notification (optional, e.g. user says "erinnere mich um 9 Uhr")

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations only declare that this is a non-readOnly, non-destructive, non-idempotent write. The description adds real behavioral context beyond that: the assignee is notified in-app and by e-mail, and the task is never visible to customers. It does not say what happens on duplicate calls or what the response contains.

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 tight sentences, front-loaded with the action and scope; the second sentence carries the notification side effect rather than padding. Nothing is redundant.

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

Completeness3/5

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

For a 10-parameter write tool with no output schema, the description covers the assignment and notification semantics well but omits what the call returns, whether unknown workerName/projectName values are created or rejected, and any retry/idempotency implications.

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 coverage is 100%, so the enum-free parameters are already fully documented in the schema. The description only echoes the field set (date, times, project, reminder) and adds no clarification on points the schema leaves implicit, such as workerName vs workerId precedence.

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 opens with a specific verb and resource ('Creates a task') and enumerates the core payload: assignee, due date, optional times, project and reminder. It is clearly distinguishable from siblings like createTimeEntry or createAssignment, though it never names them 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?

It implies the usage context (assigning work to a teammate or yourself, with a due date), but never states when to use this versus createAssignment or createTimeEntry, nor any prerequisites such as needing an existing worker or project. Usage is inferable rather than guided.

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?