Skip to main content
Glama
avivsinai

langfuse-mcp

get_session_details

Retrieve detailed session information with optional observations. Choose output as compact summary, full JSON string, or saved file.

Instructions

Get detailed information about a specific session.

Args:
    ctx: Context object containing lifespan context with Langfuse client
    session_id: The ID of the session to retrieve (unique identifier string)
    include_observations: If True, fetch and include the full observation objects instead of just IDs.
        Use this when you need access to system prompts, model parameters, or other details stored
        within observations. Significantly increases response time but provides complete data.
    output_mode: Controls the output format and detail level

Returns:
    Based on output_mode:
    - compact: Summarized session details object
    - full_json_string: String containing the full JSON response
    - full_json_file: Summarized session details object with file save info

Usage Tips:
    - For quick browsing: use include_observations=False with output_mode="compact"
    - For full data but viewable in responses: use include_observations=True with output_mode="compact"
    - For complete data dumps: use include_observations=True with output_mode="full_json_file"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesThe ID of the session to retrieve (unique identifier string)
include_observationsNoIf True, fetch and include the full observation objects instead of just IDs. Use this when you need access to system prompts, model parameters, or other details stored within observations. Significantly increases response time but provides complete data. Pairs well with output_mode='full_json_file' for complete dumps.
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?

The description discloses that include_observations 'significantly increases response time' and explains output mode behaviors (compact, full_json_string, full_json_file). Since no annotations are provided, the description carries the full burden and does well, though it omits potential side effects like file overwriting or permission requirements.

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 Args, Returns, and Usage Tips sections. It is appropriately sized for a tool with three parameters and multiple output modes. Every sentence adds value, though it could be slightly shorter without losing clarity.

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's complexity (three parameters, multiple output modes, no output schema), the description covers all essential aspects: purpose, parameter details with trade-offs, output format descriptions, and usage scenarios. It is self-contained and leaves no obvious gaps.

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%, providing baseline 3. The description adds value beyond schema by grouping parameters into usage scenarios, offering context on how include_observations and output_mode interact, and clarifying the purpose of output_mode values beyond the schema's enum descriptions.

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 'Get detailed information about a specific session,' which is a specific verb+resource. It distinguishes from siblings like fetch_sessions (plural) and get_user_sessions by focusing on a single session identified by session_id.

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?

The usage tips provide clear guidance on when to use different parameter combinations (e.g., 'For quick browsing: use include_observations=False with output_mode=compact'), and the description implies this tool is for detailed single-session retrieval. However, it does not explicitly compare to alternatives or state when not to use it.

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