Skip to main content
Glama

solve_linear_program_tool

Optimize linear objective functions with constraints for resource allocation, manufacturing, investment planning, and supply chain optimization using mathematical programming.

Instructions

Solve a linear programming problem using PuLP.

    This tool solves general linear programming problems where you want to
    optimize a linear objective function subject to linear constraints.

    Use cases:
    - Resource allocation: Distribute limited resources optimally
    - Diet planning: Create nutritionally balanced meal plans within budget
    - Manufacturing mix: Determine optimal product mix to maximize profit
    - Investment planning: Allocate capital across different investment options
    - Supply chain optimization: Minimize transportation and storage costs
    - Energy optimization: Optimize power generation and distribution

    Args:
        objective: Objective function with 'sense' ("minimize" or "maximize")
                  and 'coefficients' (dict mapping variable names to coefficients)
        variables: Variable definitions mapping variable names to their properties
                  (type: "continuous"/"integer"/"binary", lower: bound, upper: bound)
        constraints: List of constraints, each with 'expression' (coefficients),
                    'operator' ("<=", ">=", "=="), and 'rhs' (right-hand side value)
        solver: Solver to use ("CBC", "GLPK", "GUROBI", "CPLEX")
        time_limit_seconds: Maximum time to spend solving (optional)

    Returns:
        Optimization result with status, objective value, variable values, and solver info

    Example:
        # Maximize 3x + 2y subject to 2x + y <= 20, x + 3y <= 30, x,y >= 0
        solve_linear_program(
            objective={"sense": "maximize", "coefficients": {"x": 3, "y": 2}},
            variables={
                "x": {"type": "continuous", "lower": 0},
                "y": {"type": "continuous", "lower": 0}
            },
            constraints=[
                {"expression": {"x": 2, "y": 1}, "operator": "<=", "rhs": 20},
                {"expression": {"x": 1, "y": 3}, "operator": "<=", "rhs": 30}
            ]
        )
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
objectiveYes
variablesYes
constraintsYes
solverNoCBC
time_limit_secondsNo

Implementation Reference

  • The MCP tool handler `solve_linear_program_tool` decorated with @mcp.tool(). It receives raw dict inputs, passes them to the core `solve_linear_program` helper (which handles schema validation and solving), and returns the result.
    def solve_linear_program_tool(
        objective: dict[str, Any],
        variables: dict[str, dict[str, Any]],
        constraints: list[dict[str, Any]],
        solver: str = "CBC",
        time_limit_seconds: float | None = None,
    ) -> dict[str, Any]:
        """Solve a linear programming problem using PuLP.
    
        This tool solves general linear programming problems where you want to
        optimize a linear objective function subject to linear constraints.
    
        Use cases:
        - Resource allocation: Distribute limited resources optimally
        - Diet planning: Create nutritionally balanced meal plans within budget
        - Manufacturing mix: Determine optimal product mix to maximize profit
        - Investment planning: Allocate capital across different investment options
        - Supply chain optimization: Minimize transportation and storage costs
        - Energy optimization: Optimize power generation and distribution
    
        Args:
            objective: Objective function with 'sense' ("minimize" or "maximize")
                      and 'coefficients' (dict mapping variable names to coefficients)
            variables: Variable definitions mapping variable names to their properties
                      (type: "continuous"/"integer"/"binary", lower: bound, upper: bound)
            constraints: List of constraints, each with 'expression' (coefficients),
                        'operator' ("<=", ">=", "=="), and 'rhs' (right-hand side value)
            solver: Solver to use ("CBC", "GLPK", "GUROBI", "CPLEX")
            time_limit_seconds: Maximum time to spend solving (optional)
    
        Returns:
            Optimization result with status, objective value, variable values, and solver info
    
        Example:
            # Maximize 3x + 2y subject to 2x + y <= 20, x + 3y <= 30, x,y >= 0
            solve_linear_program(
                objective={"sense": "maximize", "coefficients": {"x": 3, "y": 2}},
                variables={
                    "x": {"type": "continuous", "lower": 0},
                    "y": {"type": "continuous", "lower": 0}
                },
                constraints=[
                    {"expression": {"x": 2, "y": 1}, "operator": "<=", "rhs": 20},
                    {"expression": {"x": 1, "y": 3}, "operator": "<=", "rhs": 30}
                ]
            )
        """
        result = solve_linear_program(objective, variables, constraints, solver, time_limit_seconds)
        result_dict: dict[str, Any] = result
        return result_dict
  • Registration of the linear programming tools by calling `register_linear_programming_tools(mcp)` in the main server creation function `create_mcp_server`.
    register_linear_programming_tools(mcp)
  • Pydantic schema models `Variable`, `Objective`, and `Constraint` used for input validation in the tool handler.
    class Variable(BaseModel):
        """Variable definition for optimization problems."""
    
        type: VariableType = Field(
            default=VariableType.CONTINUOUS,
            description="Type of the variable",
        )
        lower: float | None = Field(
            default=None,
            description="Lower bound of the variable",
        )
        upper: float | None = Field(
            default=None,
            description="Upper bound of the variable",
        )
    
    
    class Objective(BaseModel):
        """Objective function definition."""
    
        sense: ObjectiveSense = Field(description="Optimization sense")
        coefficients: dict[str, float] = Field(
            description="Coefficients for variables in the objective function"
        )
    
    
    class Constraint(BaseModel):
        """Constraint definition."""
    
        name: str | None = Field(
            default=None,
            description="Name of the constraint",
        )
        expression: dict[str, float] = Field(description="Left-hand side coefficients")
        operator: ConstraintOperator = Field(description="Constraint operator")
        rhs: float = Field(description="Right-hand side value")
  • Core helper function `solve_linear_program` that performs Pydantic validation and uses PuLPSolver to solve the LP problem.
    @with_resource_limits(timeout_seconds=60.0, estimated_memory_mb=100.0)
    def solve_linear_program(
        objective: dict[str, Any],
        variables: dict[str, dict[str, Any]],
        constraints: list[dict[str, Any]],
        solver: str = "CBC",
        time_limit_seconds: float | None = None,
    ) -> dict[str, Any]:
        """Solve a linear programming problem using PuLP."""
        try:
            # Parse and validate input
            obj = Objective(**objective)
            vars_dict = {name: Variable(**var_def) for name, var_def in variables.items()}
            constraints_list = [Constraint(**constraint) for constraint in constraints]
    
            # Create and solve problem
            pulp_solver = PuLPSolver(solver)
            result = pulp_solver.solve_linear_program(
                objective=obj,
                variables=vars_dict,
                constraints=constraints_list,
                time_limit=time_limit_seconds,
            )
    
            return result
    
        except Exception as e:
            logger.error(f"Linear programming error: {e}")
            return {
                "status": "error",
                "error_message": f"Failed to solve linear program: {str(e)}",
                "objective_value": None,
                "variables": {},
                "execution_time": 0.0,
                "solver_info": {},
            }
  • The registration function `register_linear_programming_tools` that defines and registers both LP and IP tools using @mcp.tool() decorators.
    def register_linear_programming_tools(mcp: FastMCP[Any]) -> None:
        """Register linear programming tools with the MCP server."""
    
        @mcp.tool()
        def solve_linear_program_tool(
            objective: dict[str, Any],
            variables: dict[str, dict[str, Any]],
            constraints: list[dict[str, Any]],
            solver: str = "CBC",
            time_limit_seconds: float | None = None,
        ) -> dict[str, Any]:
            """Solve a linear programming problem using PuLP.
    
            This tool solves general linear programming problems where you want to
            optimize a linear objective function subject to linear constraints.
    
            Use cases:
            - Resource allocation: Distribute limited resources optimally
            - Diet planning: Create nutritionally balanced meal plans within budget
            - Manufacturing mix: Determine optimal product mix to maximize profit
            - Investment planning: Allocate capital across different investment options
            - Supply chain optimization: Minimize transportation and storage costs
            - Energy optimization: Optimize power generation and distribution
    
            Args:
                objective: Objective function with 'sense' ("minimize" or "maximize")
                          and 'coefficients' (dict mapping variable names to coefficients)
                variables: Variable definitions mapping variable names to their properties
                          (type: "continuous"/"integer"/"binary", lower: bound, upper: bound)
                constraints: List of constraints, each with 'expression' (coefficients),
                            'operator' ("<=", ">=", "=="), and 'rhs' (right-hand side value)
                solver: Solver to use ("CBC", "GLPK", "GUROBI", "CPLEX")
                time_limit_seconds: Maximum time to spend solving (optional)
    
            Returns:
                Optimization result with status, objective value, variable values, and solver info
    
            Example:
                # Maximize 3x + 2y subject to 2x + y <= 20, x + 3y <= 30, x,y >= 0
                solve_linear_program(
                    objective={"sense": "maximize", "coefficients": {"x": 3, "y": 2}},
                    variables={
                        "x": {"type": "continuous", "lower": 0},
                        "y": {"type": "continuous", "lower": 0}
                    },
                    constraints=[
                        {"expression": {"x": 2, "y": 1}, "operator": "<=", "rhs": 20},
                        {"expression": {"x": 1, "y": 3}, "operator": "<=", "rhs": 30}
                    ]
                )
            """
            result = solve_linear_program(objective, variables, constraints, solver, time_limit_seconds)
            result_dict: dict[str, Any] = result
            return result_dict
    
        @mcp.tool()
        def solve_integer_program_tool(
            objective: dict[str, Any],
            variables: dict[str, dict[str, Any]],
            constraints: list[dict[str, Any]],
            solver: str = "CBC",
            time_limit_seconds: float | None = None,
        ) -> dict[str, Any]:
            """Solve an integer or mixed-integer programming problem using PuLP.
    
            This tool solves optimization problems where some or all variables must
            take integer values, which is useful for discrete decision problems.
    
            Use cases:
            - Facility location: Decide where to build warehouses or service centers
            - Project selection: Choose which projects to fund (binary decisions)
            - Crew scheduling: Assign integer numbers of staff to shifts
            - Network design: Design networks with discrete components
            - Cutting stock: Minimize waste when cutting materials
            - Capital budgeting: Select investments when partial investments aren't allowed
    
            Args:
                objective: Objective function with 'sense' and 'coefficients'
                variables: Variable definitions with types "continuous", "integer", or "binary"
                constraints: List of linear constraints
                solver: Solver to use ("CBC", "GLPK", "GUROBI", "CPLEX")
                time_limit_seconds: Maximum time to spend solving (optional)
    
            Returns:
                Optimization result with integer/binary variable values
    
            Example:
                # Binary knapsack: select items to maximize value within weight limit
                solve_integer_program(
                    objective={"sense": "maximize", "coefficients": {"item1": 10, "item2": 15}},
                    variables={
                        "item1": {"type": "binary"},
                        "item2": {"type": "binary"}
                    },
                    constraints=[
                        {"expression": {"item1": 5, "item2": 8}, "operator": "<=", "rhs": 10}
                    ]
                )
            """
            result = solve_integer_program(
                objective, variables, constraints, solver, time_limit_seconds
            )
            result_dict: dict[str, Any] = result
            return result_dict
    
        logger.info("Registered linear programming tools")
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the solver options and optional time limit, which is useful, but doesn't cover important behavioral aspects like error handling, performance characteristics, memory usage, or what happens when the problem is infeasible/unbounded. The description provides some context but leaves significant gaps.

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?

The description is well-structured with clear sections (purpose, use cases, args, returns, example) and each sentence adds value. However, the six use cases could be more concise, and the detailed example takes significant space that might be better in documentation rather than the core description.

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?

For a complex tool with 5 parameters, nested objects, no annotations, and no output schema, the description does a good job with parameters but has gaps. It doesn't explain the return structure beyond mentioning 'optimization result with status, objective value, variable values, and solver info' without details. Given the complexity and lack of structured output documentation, more completeness would be beneficial.

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

Parameters5/5

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

With 0% schema description coverage, the description provides comprehensive parameter documentation that fully compensates. Each of the 5 parameters is clearly explained with detailed semantics: objective structure, variable properties, constraint format, solver options, and time limit purpose. The example further clarifies parameter usage with concrete values.

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 'solves general linear programming problems' using PuLP, specifying it optimizes a linear objective function subject to linear constraints. This distinguishes it from sibling tools like solve_integer_program_tool or solve_assignment_problem_tool by emphasizing its general-purpose nature for linear programming rather than specific problem types.

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 six concrete use cases (e.g., resource allocation, diet planning) that clearly indicate when to use this tool. However, it doesn't explicitly state when NOT to use it or mention alternatives among the many sibling optimization tools, which would be helpful for differentiation.

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/dmitryanchikov/mcp-optimizer'

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