Skip to main content
Glama
avivsinai

langfuse-mcp

find_exceptions_in_file

Identify and retrieve exception details from a specific file within a defined time window using Langfuse observability data.

Instructions

Get detailed exception info for a specific file.

Args:
    ctx: Context object containing lifespan context with Langfuse client
    filepath: Path to the file to search for exceptions (full path including extension)
    age: Number of minutes to look back (positive integer, max 7 days/10080 minutes)
    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
filepathYesPath to the file to search for exceptions (full path including extension)
ageYesNumber of minutes to look back (positive integer, max 7 days/10080 minutes)
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
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the tool's action and output modes, including file-saving behavior for 'full_json_file', which adds useful context. However, it lacks details on permissions, rate limits, or error handling, leaving gaps for a tool that queries exception data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (purpose, Args, Returns) and uses bullet points for readability. It's appropriately sized, though the 'Args' section slightly repeats schema info. Most sentences earn their place by adding context, such as output mode details.

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?

Given the tool's complexity (querying exceptions with time-based filtering), the description is reasonably complete. It explains the core action, parameters, and output variations. With an output schema present, it doesn't need to detail return values, and it compensates for the lack of annotations by describing behavioral aspects like file-saving.

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 100%, so the schema already documents all parameters thoroughly. The description repeats some parameter info in the 'Args' section but adds minimal value beyond the schema, such as clarifying output modes in the 'Returns' section. This meets the baseline for high schema coverage.

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 clearly states the tool's purpose: 'Get detailed exception info for a specific file.' It specifies the verb ('Get') and resource ('exception info for a specific file'), making the action clear. However, it doesn't explicitly differentiate from its sibling 'find_exceptions' (which likely searches more broadly), so it doesn't reach the highest score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'find_exceptions' or 'get_exception_details', nor does it specify prerequisites or exclusions. Usage is implied by the parameters but not explicitly stated.

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