Skip to main content
Glama

Create a CRM task

dosai_create_task

A task for the owner: call, message, meeting or to-do, with a due time, optionally on a deal or a client. Editor or above.

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_id": "<workspace_id>",
      "title": "<title>"
    },
    "name": "dosai_create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
titleYes
due_atNoISO date-time with offset or Z, e.g. 2026-10-30T10:00:00Z.
deal_idNoDeal id, as returned by dosai_list_deals (a deal is a lead of the CRM).
contact_idNo
workspace_idYesCRM project (workspace) id, as returned by dosai_list_workspaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed3 schema fields changed
    • removedInput schema / properties / contact_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / deal_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / workspace_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write-and-safe-to-repeat profile is covered structurally. The description adds the role requirement ("Editor or above") and the fact that the task is assigned to the owner, which the annotations do not convey. It stops short of saying whether the owner is the caller, whether notifications fire, or what is returned on success.

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?

A single compact sentence that front-loads the resource and its qualifiers, with the permission clause last. Nothing is padded, but the noun-phrase fragment lacks an explicit verb and reads more like a field summary than an instruction, which slightly weakens immediate comprehension.

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 6-parameter mutation tool with no output schema, the definition covers fields, the enum, optional associations and the role gate reasonably well. It leaves unaddressed what the caller receives back (task id for later dosai_update_task use) and whether deal_id/contact_id may be combined, which matter for correct invocation.

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?

With only 50% schema coverage, the description meaningfully compensates: it explains the four kind values, that due_at is a due time, and that the task can be attached to a deal or a client — covering contact_id, which has no schema description at all. It also implies ownership semantics for the task. The remaining gap is that it does not clarify how deal_id and contact_id interact (mutually exclusive or both allowed).

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 definition names the resource (a CRM task) and enumerates its domain fields — kind values (call/message/meeting/todo), a due time, and optional deal or client association. It never uses an explicit creation verb, so the create action is only carried by the title and tool name, and it does not distinguish itself from the sibling dosai_update_task. Still, an agent can tell what object is produced without opening the schema.

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?

"Editor or above" states a permission prerequisite, which is genuinely useful selection context. However, there is no statement of when to choose this over dosai_update_task, dosai_create_deal or dosai_create_lead, and no exclusions or preconditions beyond the role gate. Usage is implied rather than guided.

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