Skip to main content
Glama

Future Micro Mold Lab

Plan the study sequence

plan_process_development
Read-onlyIdempotent

Given the studies already run, return the full development sequence with each one marked done or outstanding, what each fixes, what it depends on, and which study to run next. The order matters: each study fixes a setpoint the next one holds constant, so running them out of order produces numbers that do not transfer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "plan_process_development"
  }
}

Input Schema

NameRequiredDescriptionDefault
completedNoStudies already run
setpointsNoSetpoints fixed so far, from each study result

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so that ground is covered. The description earns credit beyond them by disclosing the domain constraint that each study fixes a setpoint the next holds constant, and by sketching the shape of the return value — genuine context an agent could not infer from the annotations.

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, no filler. The output contract is stated first and the ordering rationale follows as justification for the tool's existence, so the most decision-relevant information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description properly spends words on the return contents, and it explains the sequencing logic that makes the tool necessary. The one gap is the relationship between the setpoints input and the returned plan, which a caller must infer from the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented and the baseline is 3. The description does connect 'studies already run' to the completed set, but it never mentions the setpoints object or whether supplying prior setpoints changes the plan, leaving an agent to work that out from the schema alone.

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 gives a specific verb and resource — return the full development sequence given already-run studies — and enumerates what the response contains (done/outstanding status, what each study fixes, dependencies, the next study). It is clearly distinguishable from sibling tools that each run a single named study, since this one plans across them.

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?

Usage context is well established: consult this to decide what to run next, and the warning that out-of-order execution produces non-transferable numbers makes the stakes of ignoring it explicit. What is missing is an explicit exclusion or named alternative (e.g., where to go for a single study's protocol), so it stops short of the 5 tier.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources