Skip to main content
Glama

Get session with its traces

getSession

Retrieve a Langfuse session and its associated traces by providing the session id.

Instructions

Fetch a session by id, including its traces.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYes

Implementation Reference

  • src/tools.ts:92-100 (registration)
    Registration of the 'getSession' tool via server.registerTool. It accepts a 'sessionId' string (min length 1) and calls Langfuse public API GET /api/public/sessions/{sessionId}.
    server.registerTool(
      "getSession",
      {
        title: "Get session with its traces",
        description: "Fetch a session by id, including its traces.",
        inputSchema: { sessionId: z.string().min(1) },
      },
      async ({ sessionId }) => asJson(await client.get(`/api/public/sessions/${enc(sessionId)}`)),
    );
  • Handler function for 'getSession': an anonymous async function that destructures 'sessionId' from args, URL-encodes it via the 'enc' helper, and performs a GET request to the Langfuse public sessions endpoint.
    async ({ sessionId }) => asJson(await client.get(`/api/public/sessions/${enc(sessionId)}`)),
  • Input schema for 'getSession': a single required 'sessionId' field validated as a non-empty string via Zod's z.string().min(1).
    inputSchema: { sessionId: z.string().min(1) },
  • Helper 'asJson' that wraps data into an MCP text content response with pretty-printed JSON.
    const asJson = (data: unknown) => ({
      content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }],
    });
  • Helper alias 'enc' referencing encodeURIComponent, used to safely encode the sessionId in the URL path.
    const enc = encodeURIComponent;
Behavior3/5

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

The description notes that traces are included in the response, providing behavioral context beyond the schema. However, no annotations exist, and the description does not disclose other traits like read-only nature or side effects.

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 a single, front-loaded sentence with no unnecessary words. Every element earns its place.

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

Completeness3/5

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

For a simple fetch-by-id tool with one parameter and no output schema, the description is adequate but could provide more context on what a session represents or typical usage scenarios.

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?

Schema description coverage is 0%, and the description does not explain the meaning or format of sessionId. The agent must rely solely on the parameter name, which is insufficient for a single required parameter.

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 'fetch', the resource 'session by id', and the included content 'its traces'. It is distinct from sibling tools like 'getTrace' or 'listSessions'.

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 the tool is for fetching a specific session, but does not indicate when to use it versus alternatives like listSessions or getTrace. No exclusions or prerequisites are mentioned.

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/hugoles/langfuse-mcp'

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