Skip to main content
Glama

Get a dataset by name

getDataset

Fetch metadata for a dataset by providing its name. Access dataset details from Langfuse.

Instructions

Fetch metadata for a dataset by its name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datasetNameYes

Implementation Reference

  • Tool registration and handler for 'getDataset'. Calls the Langfuse API at /api/public/v2/datasets/{datasetName} to fetch a dataset by name.
    server.registerTool(
      "getDataset",
      {
        title: "Get a dataset by name",
        description: "Fetch metadata for a dataset by its name.",
        inputSchema: { datasetName: z.string().min(1) },
      },
      async ({ datasetName }) =>
        asJson(await client.get(`/api/public/v2/datasets/${enc(datasetName)}`)),
    );
  • Input schema for 'getDataset': requires a non-empty string 'datasetName'.
    inputSchema: { datasetName: z.string().min(1) },
  • src/tools.ts:205-214 (registration)
    The tool is registered via server.registerTool('getDataset', ...) inside registerTools().
    server.registerTool(
      "getDataset",
      {
        title: "Get a dataset by name",
        description: "Fetch metadata for a dataset by its name.",
        inputSchema: { datasetName: z.string().min(1) },
      },
      async ({ datasetName }) =>
        asJson(await client.get(`/api/public/v2/datasets/${enc(datasetName)}`)),
    );
  • src/tools.ts:406-406 (registration)
    'getDataset' is also listed in the TOOL_NAMES array for enumeration purposes.
    "getDataset",
  • The 'asJson' helper wraps the API response into MCP content format.
    const asJson = (data: unknown) => ({
      content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }],
    });
    
    const enc = encodeURIComponent;
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'fetch metadata,' implying a read operation, but does not mention side effects, authorization, rate limits, or error conditions.

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 a single sentence, concise and front-loaded. Every word adds value, though it could be slightly more informative without sacrificing conciseness.

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 simple interface (1 param, no output schema), the description is minimal. It does not explain what 'metadata' includes or any preconditions like the dataset must exist. Lacks completeness for a standalone definition.

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 adds no meaning beyond the parameter name. It says 'by its name,' which is already clear from the schema and field name. Does not compensate for missing schema 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 the action (fetch), the resource (metadata for a dataset), and the key identifier (by name). It effectively distinguishes from sibling tools like 'listDatasets' (which lists multiple) and 'getDatasetItem' (which gets an item within a dataset).

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 is provided on when to use this tool versus alternatives. With many sibling get/list tools, the description lacks context for selecting the appropriate tool.

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