Skip to main content
Glama

stacktrace_render

Read-onlyIdempotent

Shows a stack trace to the user as a formatted, syntax highlighted view (.NET and JavaScript). Use this whenever the user shares or asks about a stack trace, from elmah.io or from their own code, instead of repeating it in a code block. Pass the stack trace exactly as received. It does not analyze the trace; explain it in your own reply.

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": {
      "stackTrace": "<stackTrace>"
    },
    "name": "stacktrace_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoThe language of the stack trace. Leave as Auto unless detection gets it wrong.Auto
stackTraceYesThe stack trace text, exactly as received, including the exception type and message lines.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds behavior not in the annotations: the tool pushes a rendered view to the user's UI rather than returning text, and it deliberately performs no analysis. What the tool returns to the model is still unstated, but that matters less for a display-only 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?

Three sentences, zero filler, with the core action first, the usage condition second, and the agent-behavior caveat last. Every sentence carries actionable information.

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?

For a two-parameter, non-destructive display tool with no output schema, the description covers the action, the trigger condition, the input-fidelity requirement, and the division of labor between the tool and the agent's own explanation. Nothing needed to call it correctly is missing.

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 100%, so the baseline is 3, but the description adds real guidance for the required parameter: 'Pass the stack trace exactly as received,' warning against truncation or reformatting. The language parameter is only implied via '(.NET and JavaScript)' and is otherwise left to the 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?

States a specific verb and resource ('Shows a stack trace ... as a formatted, syntax highlighted view') with the supported languages named. No sibling tool in the catalog does rendering, and the description makes the rendering role unmistakable.

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

Usage Guidelines5/5

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

Explicitly says when to use it ('whenever the user shares or asks about a stack trace, from elmah.io or from their own code') and names the alternative it replaces ('instead of repeating it in a code block'). It also draws a firm boundary: 'It does not analyze the trace; explain it in your own reply.'

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