Skip to main content
Glama

HonestCRM

List tasks

list_tasks
Read-onlyIdempotent

List tasks, open by default, soonest due first. Set assignedTo to "me" for the signed-in user's own tasks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1. Default 1.
limitNoRecords per page. Default 20.
dealIdNoOnly tasks linked to this deal.
statusNoOpen tasks or finished tasks. Default open.
companyIdNoOnly tasks linked to this company.
contactIdNoOnly tasks linked to this contact.
dueBeforeNoOnly tasks due on or before this day, as YYYY-MM-DD in the user's time zone. Tasks with no due date are left out.
assignedToNo"me" for the signed-in user, or a user id. Default: everyone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The one genuinely new behavioral fact is result ordering ("soonest due first"); the open-by-default and "me" alias are already spelled out in the schema. Pagination totals and result shape are not addressed.

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?

Two short sentences, no waste, with the default scope and ordering front-loaded before the one narrowing hint. Nothing needs trimming or reordering.

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 read-only, all-optional-parameter list tool with full schema coverage and annotations, the description is serviceable but thin: it omits how filters combine, pagination expectations, and what a task record contains (no output schema exists to cover that). Adequate, with clear gaps.

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%, so every one of the eight parameters is already documented (including status default and the assignedTo "me" sentinel). The description adds no filter syntax, combination rules, or precedence guidance beyond the schema, so baseline 3 applies.

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?

Specific verb+resource ("List tasks") with default filter (open) and default ordering (soonest due first) stated up front. It does not explicitly distinguish itself from siblings like search or get_deal, but the purpose 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?

Provides implied usage guidance through defaults — tasks are open unless status is set, and assignedTo "me" scopes to the signed-in user. There is no explicit when-to-use vs. an alternative (e.g., search for free-text or complete_task for finishing work), so the agent must infer.

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