Skip to main content
Glama

Optimatika Optimisation Service

Translate a model between formats

translate
Read-onlyIdempotent

Rewrites an optimisation model from one file format to another: LP (CPLEX LP format), MPS, or EBM (ojAlgo's own).

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": {
      "model": "<model>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "translate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
modelYesThe model, as text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that all three formats are handled and that EBM is ojAlgo-specific, but it says nothing about lossy conversions (LP cannot express everything MPS can), what happens on parse failure, or how the converted model is returned.

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?

A single sentence with no filler, front-loaded with the operation and immediately followed by the concrete format set. Nothing here is redundant with the title alone.

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 3-required-parameter tool with no output schema, the definition should say what comes back (converted model text) and what failure looks like. The description covers the what but not the return or error behavior, which is the main remaining gap given annotations handle safety.

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 only 33% — only the `model` parameter has a schema description ("The model, as text"). The description partly compensates by explaining that LP means CPLEX LP format and EBM is ojAlgo's own format, which gives real meaning beyond the bare enum tokens, but `from`/`to` semantics and the expected text encoding of `model` remain thin.

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?

"Rewrites an optimisation model from one file format to another" gives a specific verb and resource, and the parenthetical list (CPLEX LP, MPS, ojAlgo's EBM) pins down the domain. It does not explicitly distinguish itself from the siblings solve/environment, but the conversion purpose is unambiguous from the text.

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?

The purpose implies the usage — convert a model before handing it to another tool — but the description never states when to translate versus when to call solve directly, nor any prerequisites (e.g. that the input model text must already be valid in the declared source format). No alternatives or exclusions are named.

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