ISO-toolset MCP

cortex-start

Start or attach to the configured Cortex MCP runtime and discover its tools so analysts can access security-vendor integrations through one gateway.

Instructions

Start or attach to the configured Cortex MCP runtime and discover its tools.

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": "cortex-start"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does add real value by disclosing the attach-if-already-running semantics (implying idempotence) and the tool-discovery side effect, but it is silent on failure modes, whether auth or configuration must pre-exist, and any side effects of starting the runtime. The output schema covers return values, so that omission is acceptable.

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; the primary action and the discovery side effect are both front-loaded.

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?

For a parameterless lifecycle tool with an output schema, the description covers what the tool does and the key attach/discover behavior. It falls short only on preconditions and error behavior, which an agent bootstrapping a runtime would benefit from knowing.

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

Parameters4/5

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

The tool takes zero parameters, which is the baseline-4 case. The description correctly implies no inputs are needed, consistent with the empty schema.

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 pair ("Start or attach") and a specific resource ("the configured Cortex MCP runtime"), plus a secondary effect ("discover its tools"). An agent can distinguish this from cortex-stop and cortex-call, though the boundary with cortex-status is not drawn.

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 only implied: an agent infers it should call this to bootstrap the runtime before invoking tools. There is no explicit when-to-use versus cortex-status or cortex-call, and no stated preconditions or when-not-to-call guidance.

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

Deploy Server