Skip to main content
Glama

mcp-server

by com.debitura

Get Case Tasks

get_case_tasks
Read-onlyIdempotent

List the open tasks (action-items) attached to one specific case — same data as list_tasks, scoped to a single case. Use this when you're already working a specific case and want just its outstanding tasks.

Note: account-level tasks that aren't tied to any one case (e.g. SignContract, AssignBankAccount — these block the whole account, not one case) never appear here; use list_tasks to see those.

See list_tasks for the full task model (auto-resolve, solutionUrl, action).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoRestrict to specific task types, e.g. ["ReplyToChat", "SignContract"]. Valid values: Generic, ReplyToChat, SelectQuoteWinner, ReviewPartner, ClientInputRequired, SignContract, MoreInfoNeeded, AssignBankAccount, CaseValidationNeedsInfo
caseIdYesDebitura case ID (GUID)
statusNoFilter by task status. "Open" (default) or "Solved".

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral context: explains that account-level tasks are excluded and references list_tasks for the full task model, enhancing transparency beyond annotations.

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, front-loaded with the primary purpose, and includes necessary clarifications in a note without unnecessary words.

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 full input schema coverage, no output schema, and annotations indicating a safe read operation, the description fully covers the tool's behavior, constraints, and relationship to siblings.

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 the description adds little beyond what the schema provides. It does imply default status 'Open' and mentions type filtering, but these are already in parameter descriptions.

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 it lists open tasks for one specific case, uses the verb 'list' with the resource 'tasks', and distinguishes from the sibling 'list_tasks' by noting scoping and exceptions.

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?

Explicitly states when to use ('when you're already working a specific case') and when not to (account-level tasks not here, use list_tasks). Names alternative sibling tool.

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

All mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a clearly distinct resource and action: case vs. tasks vs. files vs. messages vs. payments vs. account summary. The get_case_* family is broken out by specific sub-resource (activity, contract status, messages, payments, tasks), and preview_case is explicitly distinguished from create_case. list_tasks vs. get_case_tasks are scoped differently and the descriptions call out the difference.

Naming Consistency5/5

All tool names follow a consistent lowercase verb_noun pattern: create_, get_, list_, send_, upload_, preview_, ping. Even the standalone 'ping' is a common health-check convention and does not break the pattern. No camelCase or mixed verb styles appear.

Tool Count4/5

At 16 tools, the server is slightly above the typical 3-15 well-scoped range, but the breadth of the domain (case lifecycle, tasks, files, messages, payments, team management) justifies each tool. The count feels reasonable rather than bloated, earning a 4 rather than a 5.

Completeness4/5

The core workflow is well covered: preview, create, monitor (list/get, activity, payments, messages, contract status, files, tasks), communicate, and attach files. Missing operations like update_case, delete_case, or explicit task resolution are gaps, but they are often not needed in this domain since tasks auto-resolve and the partner drives legal processes. Overall, the surface is complete enough for typical agent workflows.

Resources