Skip to main content
Glama
debitura

Debitura

Official

List Tasks

list_tasks
Read-onlyIdempotent

List all open tasks across your account that require action to proceed with cases or account setup. Use as a live work queue to identify pending items like replying to chats, signing contracts, or assigning bank accounts.

Instructions

List every open task (action-item) across your whole account — things the platform needs you to do before a case (or your account) can proceed: reply to a chat, sign a contract, assign a bank account, and so on. Use get_case_tasks instead to scope this to one case.

Tasks auto-resolve once the underlying condition clears — e.g. replying to a case's chat makes its ReplyToChat task disappear on its own. Treat this as a live work queue, not a log: a task seen on one call may no longer be open on the next.

Every task carries a solutionUrl — an absolute link a human can open to resolve it in one click, whatever the type. Some types (today: ReplyToChat, ClientInputRequired, MoreInfoNeeded) additionally carry a non-null action pointing at the exact API call that resolves them — for those, call send_case_message with the task's caseId instead of sending a human to solutionUrl. Tasks without an action rely on solutionUrl alone.

Task types: Generic, ReplyToChat, SelectQuoteWinner, ReviewPartner, ClientInputRequired, SignContract, MoreInfoNeeded, AssignBankAccount, CaseValidationNeedsInfo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, starting from 1 (default 1)
typeNoRestrict to specific task types, e.g. ["ReplyToChat", "SignContract"]. Valid values: Generic, ReplyToChat, SelectQuoteWinner, ReviewPartner, ClientInputRequired, SignContract, MoreInfoNeeded, AssignBankAccount, CaseValidationNeedsInfo
statusNoFilter by task status. "Open" (default) or "Solved".
pageSizeNoResults per page (default 10, max 100)
Behavior5/5

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

The description goes beyond the annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) by disclosing that tasks auto-resolve, that it is a live work queue (not a log), and that tasks may disappear between calls. It also explains the 'solutionUrl' and 'action' field behavior, providing valuable behavioral context.

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?

The description is concise yet comprehensive, with each sentence serving a distinct purpose: stating the tool's function, guiding tool selection, explaining auto-resolution, describing output fields, and listing types. No unnecessary words or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high schema coverage, clear annotations, and the description's thorough coverage of usage, behavior, and output semantics (solutionUrl, action, task types), the tool is fully specified for an AI agent to select and invoke correctly. The lack of an output schema is compensated by the description's details.

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?

The input schema has 100% description coverage, so the description does not need to add parameter details. The description focuses on usage and behavior but does not add any new information about the parameters beyond what the schema already provides. Therefore, a baseline score of 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?

The description clearly states the verb 'list' and resource 'tasks' with the scope 'across your whole account'. It distinguishes from the sibling tool 'get_case_tasks' by specifying to use that for scoping to one case, making the purpose highly specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly provides when to use this tool vs. the alternative 'get_case_tasks', and gives detailed guidance on how to handle tasks based on the presence of an 'action' field, including when to call 'send_case_message' instead of using the 'solutionUrl'. This covers both when-to-use and when-not-to-use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/debitura/Debitura.MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server