Skip to main content
Glama

HonestCRM

Create a task

create_task

Create a task, optionally linked to a contact, company or deal, assigned to a user, and with an email reminder before it is due.

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>"
    },
    "name": "create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoExtra detail about the task.
titleYesWhat needs to be done.
dealIdNoLink the task to this deal.
dueDateNoDue day as YYYY-MM-DD in the user's time zone. Without dueTime the task is all-day.
dueTimeNoDue time as HH:mm on dueDate, 24-hour. Needs dueDate.
companyIdNoLink the task to this company.
contactIdNoLink the task to this contact.
assigneeUserIdNoThe id of the user who does the task. Default: the signed-in user.
reminderMinutesBeforeNoEmail the assignee this many minutes before the task is due. Needs dueDate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world write, so the safety profile is covered. The description adds the useful behavioral note that a reminder is sent by email to the assignee before the due time, but says nothing beyond the schema about validation failures, defaults on omitted links, or what a repeated call creates given 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 that names the action first and then the optional capabilities, with no filler or redundancy.

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 9-parameter create tool with fully documented schema and clear annotations, the description covers purpose and the optional linkage/reminder surface adequately; no output schema means return values need not be explained. It would be stronger with a note on updating or completing tasks afterward, but nothing essential to calling it correctly is missing.

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 every field carrying its own explanation (including the dueDate/dueTime and reminderMinutesBefore dependencies), so the baseline is 3. The description's summary of linking and reminders restates what the schema already documents rather than adding format, constraint, or cross-field detail.

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 ("Create a task") and enumerates the optional relationships, assignee, and reminder it supports, so an agent can immediately tell this apart from list_tasks or complete_task. It stops short of naming any sibling explicitly, but the intent is unambiguous.

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 only implied: the word "Create" signals a write operation, and the optional-link phrasing hints at when to attach a contact/company/deal. There is no explicit when-to-use, when-not-to-use, or pointer to update/complete tools for modifying or closing a task afterward, leaving the agent to infer the boundary.

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