Skip to main content
Glama

apply_planset

Expands an experiment plan set into multiple output directories, each containing a cq.yaml and plan provenance. Returns schema or validation errors for invalid input.

Instructions

Expand ExperimentPlanSet members into N output directories, each with its own cq.yaml + plan provenance. Returns rejected envelope with reason='schema_invalid'|'validation_failed' on bad input.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNo.
forceNo
plansetNoInline ExperimentPlanSet dict. Minimal example: { "schema_version": 1, "id": "sweep-001", "intent": "lr sweep", "parent_run_id": "run_baseline", "plans": [ {"id": "exp-000", "changes": [ {"op": "set_config", "key": "lr", "value": 0.01}]}, {"id": "exp-001", "changes": [ {"op": "set_config", "key": "lr", "value": 0.001}]} ] } Required: id, plans (non-empty, each member is an ExperimentPlan).
planset_fileNoPath to ExperimentPlanSet JSON file
output_patternNoPattern using {i} (zero-based index) and/or {plan_id}runs/exp{i}
Behavior3/5

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

Discloses creation of directories and error behavior, but lacks details on side effects (overwriting, auth needs, destructive actions) since no annotations exist. Partial transparency.

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?

Two sentences covering main action and error scenario. No redundant information; every word serves a purpose.

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?

Lacks description of successful return value (e.g., list of created directories) and side effect transparency. Given nested objects and no output schema, more detail is needed for full understanding.

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?

Adds meaningful descriptions for 'planset' (example, required fields), 'planset_file' (path), and 'output_pattern' (pattern format). However, 'path' and 'force' lack extra context beyond defaults.

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?

Description uses specific verb 'Expand' and resource 'ExperimentPlanSet members', clearly stating it creates output directories with config and provenance. It also distinguishes from sibling 'apply_plan' by focusing on plan sets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description implies usage for expanding plansets but does not explicitly state when to use this over alternatives like 'apply_plan' or under what conditions (e.g., multiple plans). No exclusions or prerequisites mentioned.

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/playidea-lab/pcq'

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