Skip to main content
Glama
dragosh29

Plannr MCP Server

by dragosh29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List cases

list_cases
Read-onlyIdempotent

List and filter cases such as pension transfers or mortgages by client, household, employee, status, type, or date ranges to monitor progress and reviews.

Instructions

Cases (pieces of advice work such as a pension transfer or a mortgage) with type, status, review date, completion and participants by name, filtered as GET /api/v1/cases documents: by client, household, employee, progress, review or completion date range, status or type. Case values are not returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort field; prefix with - for descending. The API's default is name.
statusesNoCase statuses (filter[status])
completedNofilter[completed]
type_uuidsNoCase type UUIDs (filter[type])
in_progressNofilter[in_progress]
max_resultsNoMost records to return; lists are fetched 100 per request, up to 10 requests
client_uuidsNoOnly cases for these accounts (filter[account_uuids])
review_afterNoOnly cases with a review date after this (filter[review_at_after])
review_beforeNoOnly cases with a review date before this (filter[review_at_before])
employee_uuidsNoOnly cases for these employees (filter[employee_account_uuids])
completed_afterNofilter[completed_after]
household_uuidsNoOnly cases for these circles (filter[circle_uuids])
completed_beforeNofilter[completed_before]
include_contact_detailsNoInclude participants' email addresses, and stop redacting emails, phone numbers and postcodes typed into case and participant names. Off by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readonly, idempotent, non-destructive behavior, so the bar is lower. The description adds genuinely useful context beyond them: 'Case values are not returned,' which warns the agent this listing omits financial data and should not be used to fetch case contents.

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?

A single long but well-structured sentence: resource definition and returned fields are front-loaded, filter dimensions follow, and the 'case values are not returned' caveat closes it. Little waste.

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

Completeness4/5

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

With 14 optional params and no output schema, the description carries the return-value burden and does so by listing returned fields and explicitly excluding case values. Adequate; it could say more about pagination or sort defaults, which the schema already covers.

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 parameter is already documented in the schema, including the include_contact_details redaction behavior. The description only restates the filter categories at a high level and adds no syntax or format detail beyond the schema.

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?

Names a specific verb and resource and enumerates the returned fields (type, status, review date, completion, participants by name). It is distinguishable from the singular get_case sibling, though it never names an alternative explicitly.

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?

The filter categories are listed, which implies when to use the tool, but there is no explicit guidance on when to prefer list_cases over get_case or how the filters compose. Usage context is inferable rather than stated.

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

Deploy Server

Other Tools