Skip to main content
Glama
KozakHou

bourne mcp

by KozakHou
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

bourne_plan

Persist and resolve an execution request against an existing inventory, preserving ambiguity and never executing the workload. Use it to plan reproducible experiments before running them.

Instructions

Persist and resolve an ExecutionRequest v2 against an existing inventory. Planning never executes the workload and preserves ambiguity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesFramework-independent execution intent with direct, Slurm, PBS, and IBM LSF backends.
inventory_referenceNoExisting inventory reference: latest, canonical ID, unique ID prefix, or @N.latest

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.8.1
    • addedInput schema / properties / inventory_reference / description
      Added value: +"Existing inventory reference: latest, canonical ID, unique ID prefix, or @N."
  2. Changed4 schema fields changedv0.8.0
    • changedInput schema / properties / request / description
      Previous value: -"Framework- and scheduler-independent execution intent for Project Bourne."New value: +"Framework-independent execution intent with direct, Slurm, PBS, and IBM LSF backends."
    • changedInput schema / properties / request / properties / execution / properties / backend / enum
      Previous value: -[
-  "auto",
-  "direct",
-  "slurm",
-  "pbs"
-]New value: +[
+  "auto",
+  "direct",
+  "slurm",
+  "pbs",
+  "lsf"
+]
    • changedInput schema / properties / request / properties / version / const
      Previous value: -1New value: +2
    • changedInput schema / properties / request / title
      Previous value: -"Project Bourne ExecutionRequest"New value: +"Project Bourne ExecutionRequest v2"
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

The 'never executes the workload' disclosure is genuinely useful behavioral context, and prior hints are absent. However, the description stops short of explaining what 'persist' actually creates or changes, whether repeated calls are safe, and what resolution fulfillment means in terms of lifecycle or side effects.

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 tightly written sentences that front-load the core action and then add the key non-execution caveat. Every clause contributes meaningful information and no space is wasted.

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?

Given the complexity of the nested ExecutionRequest schema and the breadth of sibling tools, the description provides the essential planning-vs-execution distinction but lacks workflow positioning. It does not explain how this tool fits after validation/discovery or before execution, or what the resolved result is used for.

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 description coverage is 100%, and both parameter schemas already document the request and the inventory reference. The tool description adds no additional details about the request structure, inventory_reference semantics, or how properties like 'latest' or '@N' behave.

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?

Uses a specific verb+resource ('Persist and resolve an ExecutionRequest v2') and explicitly contrasts planning with execution by saying 'Planning never executes the workload.' This distinguishes it from execution-related siblings without needing to inspect their schemas.

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?

Provides clear context for when to use the tool: against an existing inventory, to resolve a request, and specifically without executing the workload. It does not name or explicitly exclude alternatives such as bourne_validate_request, bourne_discover, or bourne_execute_plan.

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/KozakHou/project-bourne'

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