Skip to main content
Glama

CRM tasks

dosai_list_tasks
Read-onlyIdempotent

Open tasks of the CRM project (calls, messages, meetings, to-dos) with due time and the deal they belong to; status=done for finished ones.

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

Input Schema

NameRequiredDescriptionDefault
statusNo
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. Changed1 schema field changed
    • 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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds value annotations cannot: what each record carries (due time and the associated deal), which matters because no output schema exists. It omits any mention of ordering, result limits or pagination, keeping it short of a 5.

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 front-loaded sentence that packs resource, subtypes, returned fields and the status filter with no filler. The semicolon clause for status is slightly compressed for the amount of information it carries, but nothing is wasted.

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 two-parameter read-only list tool with no output schema, the description is nearly self-sufficient: it tells the agent what comes back and what the filter means. What remains missing is operational detail such as ordering, paging or caps on returned tasks, which an agent would want before calling it repeatedly.

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 coverage is only 50%, so the description must compensate, and it does: the meaning of status is spelled out (done means finished, otherwise open/due tasks), giving semantics beyond the bare enum. workspace_id semantics are delegated to the schema description, which explicitly points to dosai_list_workspaces, so the gap is acceptable.

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?

Names a specific resource (open tasks of the CRM project) plus the concrete subtypes it covers (calls, messages, meetings, to-dos) and the fields returned (due time, owning deal). This clearly separates it from generic siblings like dosai_list_deals or dosai_list_contacts, though no sibling is called out by name.

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?

"status=done for finished ones" implicitly establishes that the default behavior is open tasks, which is real usage guidance. However, it never states when to reach for this tool versus nearby options such as dosai_get_crm_today, and there are no explicit exclusions or prerequisites beyond the workspace_id reference.

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