Skip to main content
Glama

batch_dataset

Read-onlyIdempotent

Previews batch analysis inputs from per-run files, returning sample, seed, and condition identities with eligible members and exclusions before generating batch-samples.json via analysis_submit.

Instructions

Preview batch analysis inputs from collected per-run files. Return independent sample/seed/condition identities, eligible members and all exclusions. files are relative to each run directory. Use analysis_submit(batch_id,batch_files) to generate batch-samples.json and samples/<run_id>/... automatically. Partial failed-run analysis can use ordinary input_bindings with an explicit method.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>",
      "batch_id": "<batch_id>",
      "files": "<files>"
    },
    "name": "batch_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYes
task_idYes
batch_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world semantics, so the safety profile is covered. The description adds genuinely useful behavior: the output includes exclusions and eligible-member accounting, file paths are interpreted relative to each run directory, and the tool is explicitly a preview step feeding analysis_submit. It does not discuss size limits or performance, but the added context is substantial.

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?

Three sentences, front-loaded with the purpose before the workflow hint, with essentially no filler. The middle sentence is dense and mixes return-value detail with a forward reference to another tool's parameters, which slightly reduces readability but not enough to be wasteful.

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?

An output schema exists, so return values need not be spelled out, and the description sensibly covers the workflow role instead. However, for a three-parameter tool with zero schema documentation, leaving two identifiers undefined is a meaningful gap for correct invocation.

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% for three required parameters. The description only clarifies one of them, stating that files are relative to each run directory. task_id and batch_id are left entirely unexplained, and the referenced batch_files does not even match this schema's 'files' field, which risks confusion. The description does not compensate for the coverage gap.

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 opens with a specific verb+resource: 'Preview batch analysis inputs from collected per-run files.' It also clarifies what the preview returns (sample/seed/condition identities, eligible members, exclusions), which distinguishes it from the mutating sibling analysis_submit. It stops short of an explicit contrast statement in the first sentence, so it is clear but not maximally differentiated.

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?

It gives a concrete routing rule: preview here, then call analysis_submit(batch_id,batch_files) to generate batch-samples.json and samples/<run_id>/... . It also notes an escape hatch for partial failed-run analysis via ordinary input_bindings with an explicit method. There is no explicit 'do not use this when' statement, which keeps it from a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.