Skip to main content
Glama

Get a dataset item by id

getDatasetItem

Retrieve a specific dataset item using its unique ID to access detailed information from Langfuse.

Instructions

Fetch a single dataset item by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYes

Implementation Reference

  • src/tools.ts:231-239 (registration)
    Registers the 'getDatasetItem' tool with the MCP server, defining its title, description, input schema (itemId required), and handler that calls GET /api/public/dataset-items/{itemId}.
    server.registerTool(
      "getDatasetItem",
      {
        title: "Get a dataset item by id",
        description: "Fetch a single dataset item by id.",
        inputSchema: { itemId: z.string().min(1) },
      },
      async ({ itemId }) => asJson(await client.get(`/api/public/dataset-items/${enc(itemId)}`)),
    );
  • The handler for 'getDatasetItem': takes an itemId, URL-encodes it, and fetches from the Langfuse API endpoint /api/public/dataset-items/{itemId}. Results are returned as JSON text.
      async ({ itemId }) => asJson(await client.get(`/api/public/dataset-items/${enc(itemId)}`)),
    );
  • The input schema for 'getDatasetItem': a single required field 'itemId' validated as a non-empty string via Zod's z.string().min(1).
      inputSchema: { itemId: z.string().min(1) },
    },
  • Helper functions used by the getDatasetItem handler: asJson() wraps data into MCP content format, and enc() is URL-encoding (encodeURIComponent).
    const asJson = (data: unknown) => ({
      content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }],
    });
    
    const enc = encodeURIComponent;
  • The type-level registration of 'getDatasetItem' in a const array (for TypeScript type safety) listing all tool names.
      "getDatasetItem",
      "listDatasetRuns",
      "getDatasetRun",
      "getMetrics",
      "getDailyMetrics",
      "listModels",
      "getModel",
      "listProjects",
      "listComments",
      "getComment",
      "getMedia",
      "getHealth",
    ] as const;
Behavior2/5

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

With no annotations, the minimal description only indicates a read operation but fails to disclose potential errors, rate limits, or any other behavioral traits.

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?

Extremely concise, front-loaded with essential verb and noun, no redundant words.

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

Completeness2/5

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

Given the lack of output schema and annotations, the description is too minimal; it does not explain return values, errors, or context for using the tool effectively.

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

Parameters1/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 'itemId' parameter or where to obtain it, relying solely on the parameter name.

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 action (fetch), resource (dataset item), and identifier (by id), distinguishing it from sibling tools like listDatasetItems and other get* tools.

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?

No guidance on when to use this tool versus alternatives, such as needing a specific item ID or using listDatasetItems to find IDs first.

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