Skip to main content
Glama

job_getStacktrace

Retrieve a failed job's exception stacktrace to diagnose the root cause of job failures.

Instructions

Retrieve the exception stacktrace for a failed job. Use to diagnose the root cause of job failures.

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": {
      "id": "<id>"
    },
    "name": "job_getStacktrace"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. It does not state whether this is a read-only operation, what is returned when the job did not fail or has no exception, whether the stacktrace may be truncated, or any permission requirements. Only the diagnostic purpose is conveyed, so behavioral context is thin for an unannotated tool.

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?

Two short sentences, front-loading the retrieval action and following with the diagnostic use case. No filler or redundancy; every sentence contributes.

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

Completeness2/5

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

There is no output schema and no annotations, so the description should explain the return shape and the failure edge cases. It does neither, and it also leaves the meaning of the required id ambiguous, so an agent lacks information needed to call this correctly in edge cases.

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

Parameters2/5

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

The single required parameter 'id' has zero schema description coverage, so the description must compensate. It never clarifies whether 'id' means a job id, job instance id, or exception id, nor any format expectations. The schema alone leaves the agent guessing about the identifier's meaning.

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?

Names a specific verb and resource: 'Retrieve the exception stacktrace for a failed job.' An agent can distinguish this from log-listing or job-getting siblings by the diagnostic stacktrace focus. It stops short of naming an alternative explicitly, so it is clear but not fully differentiated.

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?

'Use to diagnose the root cause of job failures' gives a concrete usage context, which is exactly the trigger condition an agent needs. There is no when-not guidance (e.g., what to do if the job succeeded or the stacktrace is unavailable), which keeps it below a 5.

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

Deploy Server

Other Tools