Skip to main content
Glama

list_cases

Lists recent engineering cases with ID, title, status, and current focus so you can find the case to continue.

Instructions

List the engineer's recent cases (id, title, status, current focus) — to find the case to continue.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It helpfully discloses the return shape (id, title, status, current focus) and implies recency ordering, but it omits pagination behavior, whether closed/archived cases are included, and what happens when the engineer has no cases.

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 compact sentence that front-loads the action and resource, then lists the fields, then states intent. Nothing is redundant or padded.

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

Completeness3/5

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

For a simple one-parameter read tool with no output schema, listing the returned fields covers a lot. But the missing details about paging, scope of 'recent', and case state filtering leave an agent with unresolved decisions at call time.

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 0%, so the description should compensate, yet it never mentions the single 'limit' parameter, its default of 20, or any maximum. The parameter name is largely self-explanatory and 'recent' hints at ordering, which keeps this from being inadequate.

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?

The description uses a specific verb ('List') and resource ('the engineer's recent cases') and even enumerates the returned fields (id, title, status, current focus). It is clearly distinguishable from case-mutating siblings like open_case or resume, though it does not explicitly name a sibling.

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 trailing clause 'to find the case to continue' gives an implied usage context: call this first when you need to pick which case to work on. However, no exclusions or named alternatives are given, and it doesn't say whether to follow with resume.

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