Skip to main content
Glama
slaughters85j

SEToolBox MCP Server

by slaughters85j
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Run a SEToolBox calculation

setoolbox_run

Submit a single link budget, radar range, or EO/IR calculation request to SEToolBox and retrieve the app's verbatim result, including undetermined or error outcomes.

Instructions

Submit one calculation request to SEToolBox and wait for its result. The app does the math; this tool only writes the request file and reads the result file back verbatim.

Args:

  • tool: link_budget | radar_range | eoir

  • inputs: object keyed by schema field name. Every physical quantity is { "value": number, "unit": "<one of the field's allowed units>" }. Enum, option, and text fields are strings; integer and boolean fields are plain. Bare numbers for quantities are rejected by the app. Unknown field names are rejected. Omit what the user did not give you; the app never fills a required field from a default.

  • save (optional): { "projectName", "analysisName" }. Present means the app creates one new marked analysis in that project (created if absent). Absent means compute only.

  • displayUnits (optional): { "": "" } to choose the unit used for "value" in the result; "siValue" is always SI.

  • runId (optional): supplied by you, or generated as -<4 hex>. Must be new; the app never overwrites a result.

  • timeoutSeconds (optional): how long to wait for the result. Default from SETOOLBOX_AGENT_TIMEOUT_S (60).

Returns the result file as JSON, unchanged. Top-level keys in order: status, answer, assurance, result, warnings, run, then agentInstruction or the error fields.

  • status "ok": answer.value/unit in display units, answer.siValue/siUnit in SI; result[] echoes every derived quantity and every supplied input (state entered or pinned). Compare runs on siValue.

  • status "undetermined": answer.value is null, answer.missingInputs names what to supply, and agentInstruction says to report the quantity as not determined. This is a normal outcome, not an error.

  • status "error": error code plus field, received, allowed (when a finite set exists), and nextAction. Fix the request and resubmit with a new runId.

  • assurance is never empty. link_budget and radar_range: level "computed", citations false. eoir: level "traced", with citation and determinacy on each quantity.

A tool error (isError) means the exchange itself failed: folder missing, bad or duplicate runId, or timeout. On timeout the request stays queued; the app processes it when it is running and in front, and setoolbox_get_result returns it later. Never resubmit under the same runId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
saveNoCreate one saved analysis.
toolYesOne of link_budget, radar_range, eoir.
runIdNoThe request's runId.
inputsYesField name to value, per schema/<tool>.json.
displayUnitsNoField name to display unit.
timeoutSecondsNoSeconds to wait for the result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover only safety flags; the description adds substantive behavior: it writes and reads files, runIds are never overwritten, timeouts leave the request queued, and error semantics map to nextAction. This is far beyond what the structured fields disclose.

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?

Long but well-structured with Args and Returns sections, front-loaded with the core action. Given six parameters and a complex result contract, every sentence carries usable information.

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

Completeness5/5

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

No output schema exists, so the description carries the return-value burden and does so thoroughly: top-level key order, status ok/undetermined/error semantics, assurance levels per tool, and tool-error conditions. Nothing material for correct invocation is missing.

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?

Schema coverage is 100% but the schema descriptions are terse; the description adds the quantity format ({value, unit}), rejection of bare numbers and unknown fields, no default-filling, save-vs-compute semantics, displayUnits vs siValue, and runId/timeout behavior. This meaningfully exceeds the schema.

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?

States a specific verb and resource ('Submit one calculation request to SEToolBox and wait for its result') and clarifies the tool's actual role ('only writes the request file and reads the result file back verbatim'). An agent can distinguish it from siblings like setoolbox_get_result directly 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 Guidelines4/5

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

Gives clear operational guidance: omit inputs the user did not supply, never resubmit under the same runId, and use setoolbox_get_result to retrieve a result after a timeout. It does not explicitly state when to prefer this over every alternative sibling, but the retrieval-path routing is strong.

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

Deploy Server

Other Tools