Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Create Crm Task

create_crm_task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoFree-text notes.
titleYesWhat to do, e.g. "Send pricing to Jane".
deal_idNoLink a deal (query_deals `id`).
due_dateNoThe day it's due, YYYY-MM-DD. Use resolve_date first for words like "next Friday". Omit for no due date.
person_idNoLink a person (query_people `id`).
company_idNoLink a company (query_companies `id`).
on_behalf_ofNoAn agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.
assignee_emailNoWho should do it, an active teammate's email from list_teammates (not an invited one). Default: the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / on_behalf_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
+}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare it is not read-only and not destructive, so the description adds real value: the task is team-visible, may link to person/company/deal or stand alone, and critically sends no reminder/alarm. That 'no notification' trait is a non-obvious behavioral fact an agent must relay to users.

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?

Front-loads the purpose, follows with examples and a caveat, then a returns note. Structured and readable; the sentence about team visibility and the alarm caveat both earn their place, though there is minor redundancy between the examples and the earlier 'to-do' phrasing.

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?

With no output schema, the inline returns tag explains the created task's shape ('same shape as a query_crm_tasks row'). Annotations cover the safety profile and schema covers all parameters, leaving only minor gaps such as permission/assignment constraints not stated in prose.

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 each of the 8 parameters is already documented in the schema. The description adds the linking model ('stand alone or link to a person, a company and/or a deal'), which reinforces the relationship among person_id/company_id/deal_id but adds little beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a task...in the user's CRM') and clarifies scope by noting it appears on the team Tasks view and on a linked deal. It is easily distinguished from update_crm_task and query_crm_tasks (the latter named for the return shape).

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 concrete usage examples ('remind me to send pricing to Jane on Friday', 'add a task to follow up with Acme') that anchor when to reach for it, plus a clear caveat that it produces no notification. It does not explicitly contrast against update_crm_task or other task tools, so no exclusions are covered.

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

All Sliq toolsInspect
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