Skip to main content
Glama

Get Case

getCase
Read-onlyIdempotent

Get a case by ID. Returns the case, its event history, and every case-approval batch ever created on the case (newest first).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "case_id": "<case_id>"
    },
    "name": "getCase"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idYesThe case's unique identifier
include_blockersNoAlso return `blocker` on each case: for a case waiting to start, why the dispatcher cannot start it now, or null when nothing blocks it. Off by default, because it adds database reads; when off, `blocker` is left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_blockers
      Added value: +{
      +  "description": "Also return `blocker` on each case: for a case waiting to start, why the dispatcher cannot start it now, or null when nothing blocks it. Off by default, because it adds database reads; when off, `blocker` is left out.",
      +  "enum": [
      +    "true",
      +    "false"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavioral context by saying it returns the case, its event history, and every approval batch newest first, which warns the agent about a potentially large or multi-part response.

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?

It is two sentences with no filler. The core lookup behavior is front-loaded, and the return contents follow immediately.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden and does so adequately: it names the case, event history, and approval batches with ordering. Combined with full schema coverage and read-only annotations, an agent has enough information to call this correctly.

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%, so both case_id and include_blockers are already documented in the schema. The description only reinforces that lookup is by ID and says nothing extra about include_blockers, so it does not add meaning beyond the structured schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Get a case by ID.' The 'by ID' scope clearly distinguishes it from listCases and searchCases, so an agent can tell what it does without opening the schema.

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?

Usage is implied by 'by ID,' which suggests this is the direct-lookup tool rather than a list or search tool. However, the description never explicitly says when to use it instead of listCases or searchCases, nor does it state exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources