list_case_filesList all documents attached to a case: file name, document type, description, upload date, and a time-limited SAS download URL. Each file also carries downloadUrlExpiresAt (UTC) — when the download URL stops working, so a cached URL can be refreshed in time. Use upload_case_file to attach new documents.
| Name | Required | Description | Default |
|---|---|---|---|
| caseId | Yes | Debitura case ID (GUID) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which the description aligns with. It adds valuable behavioral context: the download URL is time-limited and includes an expiry field, which helps the agent understand caching behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three concise sentences with no fluff. The first sentence summarizes the purpose and return data, the second adds an important behavioral detail, and the third directs to a sibling tool. It is front-loaded and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite lacking an output schema, the description fully explains the return fields, including the downloadable URL and its expiry. The input is simple (caseId). It also references the upload sibling, making the context complete for agent usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter caseId is fully described in the schema as a GUID. The description does not add further parameter details, but schema coverage is 100%, so the baseline applies. The description does not detract and is sufficient.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists all documents attached to a case and enumerates the specific fields returned (file name, document type, description, upload date, SAS URL). It distinguishes from the sibling tool upload_case_file. The title and context reinforce this.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides a clear alternative (upload_case_file to attach documents) and a usage note about refreshing the cached URL before expiry. It implies when to use this tool (to list documents) but does not explicitly state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or action—creation, preview, listing, detail, and case-specific sub-resources (activity, contracts, messages, payments, tasks, files). The potentially overlapping task tools (list_tasks vs get_case_tasks) are explicitly cross-referenced and scoped differently.
Consistent verb_noun pattern throughout: create_, get_, list_, send_, upload_, preview_. Case-specific reads use get_case_* suffix pattern, and ping is the only utility exception.
16 tools is slightly above the ideal 3-15 range, but each tool earns its place in a comprehensive case-management API; no redundant tools.
Core lifecycle is covered (preview, create, list, get, sub-resources, messaging, file upload). Minor gaps include no case update/withdraw and no direct resolution for task types like SelectQuoteWinner, but these are mostly platform-controlled or handled via solutionUrl.