Skip to main content
Glama

Get Case Actions

pega.get_case_actions

Retrieve available actions for a Pega case or fetch specific action details using a case identifier to manage case operations.

Instructions

Use this tool to discover available actions for a case or fetch a specific action definition. Required input: caseId. Optional inputs: actionId, viewType, excludeAdditionalActions, originChannel. Returns: { ok: true, data: { actions: } } on success. Standard failure format: { ok: false, error: { code, message, suggestion? } }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseIdYesUnique case identifier/handle.
actionIdNoOptional action identifier. When provided, returns action-level details.
viewTypeNoOptional view type hint used when actionId is provided.
excludeAdditionalActionsNoOptional flag used with actionId to exclude additional actions from the payload.
originChannelNoOptional channel hint, for example Web or Mobile.

Implementation Reference

  • The execute function that handles the tool logic for pega.get_case_actions.
    execute: async ({ pegaClient }, input) => {
      return withCaseAccessGuard(pegaClient, input, async () => {
        const actions = await pegaClient.getCaseActions(input.caseId, {
          actionId: input.actionId,
          viewType: input.viewType,
          excludeAdditionalActions: input.excludeAdditionalActions,
          originChannel: input.originChannel
        });
        return {
          actions
        };
      });
    }
  • The definition of the pega.get_case_actions tool.
    export const getCaseActionsToolDefinition = defineTool({
      name: "pega.get_case_actions",
      title: "Get Case Actions",
      description: [
        "Use this tool to discover available actions for a case or fetch a specific action definition.",
        "Required input: caseId.",
        "Optional inputs: actionId, viewType, excludeAdditionalActions, originChannel.",
        "Returns: { ok: true, data: { actions: <upstream payload> } } on success."
      ].join(" "),
      inputSchema: getCaseActionsSchema,
      invalidInputMessage: "caseId is required",
      execute: async ({ pegaClient }, input) => {
        return withCaseAccessGuard(pegaClient, input, async () => {
          const actions = await pegaClient.getCaseActions(input.caseId, {
            actionId: input.actionId,
            viewType: input.viewType,
            excludeAdditionalActions: input.excludeAdditionalActions,
            originChannel: input.originChannel
          });
          return {
            actions
          };
        });
      }
    });
Behavior3/5

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

Annotations are absent, so description carries full burden. It discloses return format structure ({ ok: true/false, data/error }) which helps, but omits safety profile (read-only vs destructive), rate limits, or auth requirements despite mutation-sounding siblings existing.

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

Conciseness4/5

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

Efficiently structured with purpose first, then inputs, then outputs. Each sentence delivers distinct information (functionality, input cardinality, return contracts). Slightly verbose in documenting JSON return structure inline.

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?

Adequately compensates for missing output schema by documenting both success and failure response formats. With 5 parameters and good schema coverage, the description provides sufficient context to invoke the tool, though workflow relationships could be clearer.

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%, establishing baseline 3. Description categorizes parameters as 'Required' and 'Optional' which mirrors the schema but adds no additional semantic context (e.g., example values for originChannel, relationship between actionId and viewType).

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?

States specific verbs ('discover', 'fetch') and resource ('actions for a case'), clearly identifying it queries case actions. Lacks explicit differentiation from sibling 'submit_case_action' (discovery vs execution).

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?

Implies usage by delineating required (caseId) vs optional inputs, but provides no explicit guidance on when to use versus 'get_case' or workflow sequencing before 'submit_case_action'.

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