Skip to main content
Glama

run_eval_dataset

Run a golden dataset against a target model to detect regressions. Scores outputs with a judge model and records eval scores for A/B comparison across runs.

Instructions

Run a golden dataset against a target model and produce a regression verdict (POST /v1/eval-datasets/:id/run, Pro+ only). Feeds each item's inputText to targetModel, has gpt-4o-mini score the outputs against the default criteria plus expectedOutput, and records eval_scores (regression A/B). Results can be compared across runs with compare_eval_runs. Run records are excluded from production cost / analytics / alert aggregation. Cost: item count x criteria count LLM calls. 503 in environments without OPENAI_API_KEY provisioned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datasetIdYesId of the dataset to run (list_eval_datasets.datasets[].id)
judgeModelNoJudge model (omit = gpt-4o-mini). Only OpenAI models present in the pricing table.
targetModelYesModel to measure regressions for (only OpenAI models present in the pricing table, e.g. 'gpt-4o-mini'). Unknown models get 400.
idempotencyKeyNoOpaque key for retry dedup (UUID recommended, 200 char cap). Re-POSTing the same key returns the existing run (double-billing prevention).
Behavior5/5

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

Without annotations, the description fully discloses behavioral traits: feeds inputText to targetModel, uses gpt-4o-mini for scoring against criteria, records eval_scores, and explains idempotencyKey for dedup. It also notes cost implications and environment dependencies.

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 concise (about 100 words) and well-structured, with front-loaded main action. Every sentence adds unique information without redundancy.

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?

Despite no output schema, the description covers essential aspects: what the tool does, how it works, cost model, idempotency, error conditions, and comparison with sibling tools. It is complete for a mutation tool with 4 parameters.

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%, but the description adds value by explaining default for judgeModel, restrictions for targetModel (OpenAI models only), and the purpose of idempotencyKey (retry dedup and double-billing prevention).

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 tool runs a golden dataset against a target model to produce a regression verdict. It specifies the HTTP method and endpoint, distinguishes from siblings like compare_eval_runs, and mentions the Pro+ plan restriction.

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 description provides explicit context: results can be compared with compare_eval_runs, run records are excluded from production cost/analytics/alert aggregation, and it warns about cost and 503 errors without API key. It doesn't explicitly state when not to use, but offers strong guidance.

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/argosvix/mcp-server'

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