Skip to main content
Glama

executor_status

Reports the local executor's server status, available and active models, context length, probed capabilities, and command confinement so you can verify readiness before delegating tasks.

Instructions

State of the local executor: server, models, which one is in use, its context length, what it can do (when it has been probed) and how its commands are confined.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it does add genuinely useful behavior: capability data is only populated after probing, and reported commands are described as confined. It does not explicitly state that the call is read-only and side-effect free, which a zero-parameter status tool would benefit from asserting.

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?

A single front-loaded sentence with no filler, listing the reported facets in a logical order from server to confinement. The line break mid-parenthetical is only a formatting blemish, not a structural problem.

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?

An output schema exists, so the description need not restate return values, and the enumerated facets plus the probe-dependency caveat cover what an agent needs to interpret a status report. The only missing piece is an explicit statement that the call is a safe read with no side effects.

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, so the baseline of 4 applies; there is nothing parameter-wise for the description to compensate for, and it does not waste space restating schema content.

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?

The description names the resource (the local executor) and enumerates exactly what state is reported: server, models, the model in use, its context length, capabilities, and command confinement. That makes it distinguishable from executor_probe, which presumably performs the probing rather than reporting already-collected state.

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 rather than stated: the phrase 'when it has been probed' hints that capability data depends on a prior probe, but the description never says to call executor_probe first or when to prefer this over check_lmstudio_status. An agent can infer this is an inspection call, but there are no explicit when/when-not rules.

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