Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Update Crm Task

update_crm_task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clearNoFields to empty: 'due_date', 'person', 'company', 'deal'.
notesNoReplace the notes entirely. To add to them, use notes_append instead.
titleNoNew title.
statusNo'done' to complete it, 'open' to reopen it.
deal_idNoLink this deal instead (query_deals `id`).
task_idYesThe task's id (query_crm_tasks).
archivedNotrue deletes the task (reversible), false restores it. A deleted task can only be changed in a call that also restores it (archived=false).
due_dateNoNew due day, YYYY-MM-DD.
person_idNoLink this person instead (query_people `id`).
company_idNoLink this company instead (query_companies `id`).
notes_appendNoAdd this as a new paragraph at the end of the notes.
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_emailNoReassign to this active teammate's email from list_teammates (not an invited one).

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.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description earns its keep by explaining that the delete is a soft, reversible archive ("hides the task but keeps it, so archived=false brings it back"), which is exactly the reason destructiveHint is false and would otherwise be invisible. It also bounds scope by naming the mutation it cannot perform and describes the return payload's shape relative to a sibling query.

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?

Front-loaded with the operation list in the first sentence, then prerequisites, then the delete semantics, then the exclusions. The summary/returns structure is used purposefully and no sentence is filler.

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 13-parameter mutation with no output schema, the description is unusually complete: it names the id source, explains the archive flag, scopes out what it cannot change, and the returns block stands in for the missing output schema. The remaining gap is conflicting-parameter behavior, which matters for a tool with both notes and notes_append and a clear list.

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?

Schema description coverage is 100%, so the schema already carries per-parameter meaning and the baseline is 3. The description adds conceptual framing above the schema — the delete/restore toggle and the fact that operations are all in-place changes to one existing task — but it does not address interaction between parameters (e.g., notes vs notes_append, or clear vs due_date), so it goes only slightly past baseline.

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 ("Change a CRM task") and then enumerates the full operation set: complete/reopen, reschedule, rename, reassign, edit notes/links, delete and restore. That enumeration lets an agent distinguish it from create_crm_task, query_crm_tasks, and update_deal without opening any sibling schema.

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 the prerequisite route for the required parameter ("Get the id from query_crm_tasks") and an explicit when-not with a redirect (follow-up suggestions not yet added by the user must be handled on the Tasks view). It does not contrast itself against create_crm_task or update_deal for adjacent intents, so it stops short of a full routing rule set.

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