Skip to main content
Glama

crash_threads

List threads in a loaded crash dump to find the faulting thread or inspect thread states, with limit and offset pagination for targeted review.

Instructions

List threads in the loaded dump.

Use to find the faulting thread or inspect thread states. Supports limit/offset pagination.

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": "crash_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does establish that this is a read-style listing operation over the currently loaded dump and that it paginates, which is the key safety context for a non-mutating tool. It leaves unstated what happens when no dump is loaded (presumably an error) and gives no hint about result ordering, so disclosure is adequate but not rich.

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 with the core action and scope front-loaded, followed by usage and then pagination. No sentence is filler and nothing important is buried.

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 simple two-optional-parameter listing tool with an output schema that documents return values, the description covers purpose, usage, and pagination adequately. The only meaningful gap is that it does not state the prerequisite failure mode or thread ordering.

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 must compensate, and it does partially by naming both parameters and framing them as pagination ('limit/offset'). It does not add defaults, bounds, or what the offset is indexing into (thread order), so the two optional parameters remain only partly explained.

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 gives a specific verb and resource ('List threads') scoped to 'the loaded dump', which immediately tells an agent this returns thread data rather than stacks, disassembly, or summaries. It does not explicitly contrast itself with siblings like crash_stack, but the resource it names is distinct enough to select correctly.

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

Usage Guidelines4/5

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

It supplies concrete use cases ('find the faulting thread or inspect thread states'), which is real when-to-use guidance rather than a restatement of the name. It stops short of exclusions or pointing at an alternative tool for deeper per-thread inspection, so it is clear context but not full routing guidance.

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