Skip to main content
Glama
Sign In
SEToolBox MCP Server

SEToolBox MCP Server

by slaughters85j
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List SEToolBox projects

setoolbox_list_projects
Read-onlyIdempotent

List all saved SEToolBox projects with IDs, dates, and per-tool record counts by reading the app's local exchange file; requires the app running with agent runs allowed.

Instructions

List every project in the user's SEToolBox store: id, name, dateCreated, lastModified, and counts of records per tool family (tpmDataList, statisticalTools, massBudgetProjects, budgetTools, spacePowerBudgetProjects, nonSpacePowerBudgetProjects, linkBudgetAnalyses, radarRangeAnalyses, eoirAnalyses).

Goes through the same folder exchange as a run, so the app must be running with agent runs allowed. Returns the result file verbatim; the payload is under "data.projects". Nothing in the app changes.

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": "setoolbox_list_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutSecondsNoSeconds to wait for the result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds real context beyond them: the folder-exchange mechanism, the runtime precondition that the app must be running, and the verbatim file return with payload under 'data.projects'. 'Nothing in the app changes' usefully reinforces the read-only annotation; only limits like rate/timeouts are unaddressed.

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?

Front-loads the purpose, then follows with behavioral and output details in a logical order. The long enumeration of tool families is informative but slightly verbose; otherwise no wasted sentences.

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?

For a list tool with no output schema, the description supplies the field list, the payload location ('data.projects'), the return mechanism, and the runtime precondition. An agent has everything needed to call and interpret it correctly.

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?

With a single parameter and 100% schema description coverage, the schema fully documents timeoutSeconds, so the baseline of 3 applies. The description adds no additional parameter meaning.

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?

States a specific verb and resource ('List every project in the user's SEToolBox store') and enumerates the exact fields returned, so an agent knows precisely what this yields. It does not explicitly differentiate itself from siblings like setoolbox_list_runs or setoolbox_read_project, so it falls short of a 5.

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?

Usage is implied by the resource name, and it discloses a precondition ('the app must be running with agent runs allowed'), but it never states when to prefer this over alternatives such as list_runs or read_project, nor any exclusion conditions.

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