Skip to main content
Glama
avivsinai

langfuse-mcp

get_exception_details

Retrieve detailed exception information for a specific trace or span. Choose compact summary, full JSON string, or save to file.

Instructions

Get detailed exception info for a trace/span.

Args:
    ctx: Context object containing lifespan context with Langfuse client
    trace_id: The ID of the trace to analyze for exceptions (unique identifier string)
    span_id: Optional span ID to filter by specific span (unique identifier string)
    output_mode: Controls the output format and detail level

Returns:
    Based on output_mode:
    - compact: List of summarized exception details
    - full_json_string: String containing the full JSON response
    - full_json_file: List of summarized exception details with file save info

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trace_idYesThe ID of the trace to analyze for exceptions (unique identifier string)
span_idNoOptional span ID to filter by specific span (unique identifier string)
output_modeNoControls the output format and action. 'compact' (default): Returns a summarized JSON object optimized for direct agent consumption. 'full_json_string': Returns the complete, raw JSON data serialized as a string. 'full_json_file': Returns a summarized JSON object AND saves the complete data to a file.compact

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full burden. It explains behavior well by detailing parameters and return values based on output_mode. It does not disclose potential side effects or rate limits, but for a read operation the transparency is strong.

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?

The description is well-structured with 'Args' and 'Returns' sections. It is concise (approximately 6 sentences) and every sentence provides essential information without redundancy.

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?

Given the tool has 3 parameters, a clear output schema implied by the returns, and no nested objects, the description fully covers all aspects. It explains all output modes and addresses both optional and required parameters.

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

Parameters5/5

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

The input schema has 100% coverage with descriptions for all three parameters. The description adds significant value by explaining the return values per output_mode, which goes beyond the schema's parameter definitions. Enumerations for output_mode are clearly described.

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 clearly states the verb 'Get' and the resource 'detailed exception info for a trace/span'. It distinguishes from siblings like 'find_exceptions' and 'find_exceptions_in_file' by focusing on a specific trace/span rather than searching or file operations.

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?

The description implies usage for retrieving exception details of a specific trace/span, and mentions optional filtering by span_id and output mode. However, it does not explicitly state when to use this tool versus alternatives like 'find_exceptions' or 'find_exceptions_in_file', nor does it provide when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/avivsinai/landfuse-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server