Skip to main content
Glama

open_case

Start a new investigation case by recording the first symptom as the engineer stated it; returns a case_id to reuse for all related evidence and next steps.

Instructions

Start a new investigation case. Title = one line, the first symptom as the engineer stated it. Returns case_id; reuse it for the rest of this problem.

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": {
      "title": "<title>"
    },
    "name": "open_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden. It does disclose the most important unseen behavior — that the call returns a case_id that must be reused — which is valuable given there is no output schema. However, it says nothing about persistence, whether a case can be deleted or duplicated, or whether any session/workspace context is required for a mutation that creates durable state.

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?

Three short sentences, no waste, and the core purpose is front-loaded before the parameter guidance and the return-value note. Every sentence adds information.

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?

For a one-parameter creation tool with no output schema, the definition covers purpose, parameter meaning, and return value — enough to call it correctly. What is missing is the surrounding lifecycle: whether repeated calls create duplicates and whether the returned id is scoped to a session.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description has to define the sole parameter, and it does: 'one line, the first symptom as the engineer stated it' gives both a formatting constraint and content guidance that the bare 'title: string' does not. It stops short of a length limit or an example, which keeps it at 4 rather than 5.

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 a specific verb and resource: 'Start a new investigation case.' An agent can distinguish this from list_cases or resume on the name and verb alone, though the definition never contrasts it with the closest sibling open_thread, which also creates a container.

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 rather than stated: you call it at the beginning of a problem. The clause 'reuse it for the rest of this problem' indirectly discourages opening a second case mid-investigation, but there is no explicit when-to-use versus open_thread/resume guidance and no prerequisites listed.

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