Skip to main content
Glama
Sign In
SEToolBox MCP Server

SEToolBox MCP Server

by slaughters85j
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List recent runs

setoolbox_list_runs
Read-onlyIdempotent

List recent SEToolBox run results from the out/ folder, newest first, for read-only auditing. Shows run ID, file, tool, status, timestamp, analysis ID, and error code; limit 20 by default, up to 200.

Instructions

List recent results in out/, newest first: runId, file name, tool, status, timestamp, analysisId (when the app saved an analysis), and the error code for error results. Default limit 20, maximum 200. Read-only audit view.

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_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description goes further by disclosing ordering (newest first), the default and maximum limit, and the shape of returned rows, which is genuinely useful context beyond the annotations.

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 sentences, front-loaded with the core action and scope, then the parameter bounds and safety tag. No filler; every clause adds information.

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

Completeness4/5

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

With no output schema, the description usefully enumerates returned fields and ordering, and covers limit bounds. It stops short of mentioning pagination or how to fetch a single run's details, but for a simple list tool it is largely complete.

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 there is only one parameter; the description's 'Default limit 20, maximum 200' essentially restates schema constraints. Baseline 3 applies since the schema already carries the semantics.

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 (List) and resource (recent runs/results in out/), plus ordering (newest first) and the returned fields. An agent can distinguish this from siblings like get_result or list_tools from the description alone.

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 tagline 'Read-only audit view' implies a browsing/inspection use case, but no explicit when-to-use vs alternatives is given (e.g., when to prefer get_result for a specific run, or list_tools for schemas). Usage is implied rather than stated.

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