Skip to main content
Glama

Get Cases

pega.get_cases

Retrieve and list cases from Pega systems with optional limit parameter for managing case operations.

Instructions

Use this tool to list cases. Optional input: limit. Returns: { ok: true, data: { cases: [...] } } on success. Standard failure format: { ok: false, error: { code, message, suggestion? } }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoOptional max number of cases to return.

Implementation Reference

  • Definition and execution logic for pega.get_cases tool.
    export const getCasesToolDefinition = defineTool({
      name: "pega.get_cases",
      title: "Get Cases",
      description: [
        "Use this tool to list cases.",
        "Optional input: limit.",
        "Returns: { ok: true, data: { cases: [...] } } on success."
      ].join(" "),
      inputSchema: getCasesSchema,
      invalidInputMessage: "Invalid input. Use optional field: limit",
      execute: async ({ pegaClient }, input) => {
        const cases = await pegaClient.getCases();
        const limited = typeof input.limit === "number" ? cases.slice(0, input.limit) : cases;
    
        return toolSuccess({
          cases: limited
        });
      }
    });
Behavior3/5

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

No annotations provided, so description carries full burden. It adds valuable return structure documentation (success and failure JSON formats) compensating for the missing output schema. However, it omits critical safety information (read-only vs destructive), pagination behavior, and case structure details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Contains filler phrase 'Use this tool to' that wastes space. Front-loading is reasonable but the mixing of input specification with return format documentation creates slight structural awkwardness. No redundant sentences beyond the optional input mention.

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?

Reasonably complete for a simple listing tool with one optional parameter. Return format description compensates for lack of output schema. However, missing safety characteristics (read-only status) and sibling differentiation given the presence of 'get_case'.

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% (limit parameter fully documented). Description merely repeats 'Optional input: limit' without adding semantics about default behavior when omitted, or valid use cases for the 1-500 range.

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?

Clearly states the tool 'list cases' with specific verb and resource. However, it fails to distinguish from sibling tool 'get_case' (singular), which likely retrieves a specific case by ID versus listing multiple cases.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no guidance on when to use this tool versus the singular 'get_case' or other sibling tools. No mention of prerequisites, filtering capabilities, or search patterns.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/amirmcs/Pega-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server