Skip to main content
Glama

Get a score configuration by id

getScoreConfig

Retrieve a specific score configuration by providing its unique identifier.

Instructions

Fetch a single score configuration by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
configIdYes

Implementation Reference

  • src/tools.ts:142-150 (registration)
    Registration of the 'getScoreConfig' tool on the MCP server via server.registerTool, including the input schema (configId: z.string().min(1)) and the handler that calls client.get('/api/public/score-configs/${enc(configId)}').
    server.registerTool(
      "getScoreConfig",
      {
        title: "Get a score configuration by id",
        description: "Fetch a single score configuration by id.",
        inputSchema: { configId: z.string().min(1) },
      },
      async ({ configId }) => asJson(await client.get(`/api/public/score-configs/${enc(configId)}`)),
    );
  • The handler function for getScoreConfig: an async lambda that takes { configId }, encodes it, and calls client.get on the Langfuse public API endpoint /api/public/score-configs/{configId}.
    async ({ configId }) => asJson(await client.get(`/api/public/score-configs/${enc(configId)}`)),
  • Input schema definition for getScoreConfig: expects a single required string 'configId' with min length 1.
    inputSchema: { configId: z.string().min(1) },
  • src/tools.ts:392-420 (registration)
    Exported TOOL_NAMES array listing all tool names, including 'getScoreConfig' at line 402.
    export const TOOL_NAMES = [
      "listTraces",
      "getTrace",
      "listObservations",
      "getObservation",
      "listSessions",
      "getSession",
      "listScores",
      "getScore",
      "listScoreConfigs",
      "getScoreConfig",
      "listPrompts",
      "getPrompt",
      "listDatasets",
      "getDataset",
      "listDatasetItems",
      "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?

No annotations provided. Description only says 'Fetch' implying read-only, but does not disclose error behavior, authentication needs, or return characteristics.

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

Conciseness2/5

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

While short, the description is under-specified and omits critical information, making it insufficient rather than concise.

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 no output schema or annotations, the description fails to provide adequate context about return values, error conditions, or behavioral details.

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 coverage is 0%; description adds no meaning to the configId parameter beyond its schema definition (string, minLength 1). Does not explain format or valid values.

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 action (fetch) and resource (score configuration) and specifies retrieval by id, but does not differentiate from other get tools like getScore or getComment.

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 vs siblings like listScoreConfigs. Lacks context about prerequisites or alternatives.

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