Skip to main content
Glama

mcp-server

by com.debitura

List Cases

list_cases
Read-onlyIdempotent

List the creditor's debt collection cases with pagination, status filtering, and sorting. Returns compact case summaries: reference, debtor name + country, amounts, lifecycle, partner, key dates. Use get_case for full detail on a specific case.

Lifecycle values (statuses filter and output): PendingContractSigning · PendingVerificationInternal · PendingVerification · NeedsAdditionalDetails · Leads · LeadsQuoteGiven · Active · Paused · Closed · Merged

Sortable fields: DateCreated · DateUpdated · DateFinished · DateCollectionStarted · DueDate · Date · GrossAmount · Remainder · InterestFees · CollectionFees Sort format: Field:asc or Field:desc, e.g. GrossAmount:desc

Note: results include the creditor's own test cases; the isTestCase flag on each case marks them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, starting from 1 (default 1)
sortNoSort expression: Field:asc or Field:desc. Valid fields: DateCreated, DateUpdated, DateFinished, DateCollectionStarted, DueDate, Date, GrossAmount, Remainder, InterestFees, CollectionFees. Example: GrossAmount:desc
pageSizeNoResults per page (default 10, max 100)
statusesNoFilter by lifecycle status. Values: PendingContractSigning, PendingVerificationInternal, PendingVerification, NeedsAdditionalDetails, Leads, LeadsQuoteGiven, Active, Paused, Closed, Merged

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. The description adds that it returns compact summaries and includes test cases marked by isTestCase, which is useful 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?

Description is well-structured with a concise first sentence, followed by detailed bullet points. No unnecessary words, each sentence adds unique value.

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?

Despite no output schema, it describes return fields and the isTestCase flag. Covers pagination, filtering, sorting, and a note about test cases. Complete for a list tool.

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 baseline is 3. The description lists parameters and explains sort format and enum values, adding minor value over schema. No major shortcomings.

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 tool lists debt collection cases with pagination, status filtering, and sorting. It specifies the resource and actions, and distinguishes itself from get_case for full detail.

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?

The description explicitly mentions using get_case for full details, implying list_cases for summaries. It also details filtering and sorting. However, it could more explicitly state when not to use it (e.g., for creation).

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