Skip to main content
Glama

executor_status

Check whether the installed DeepSeek interface is compatible without starting a model, so you can verify setup before running tasks.

Instructions

Check installed DeepSeek interface compatibility without starting a model.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. "Without starting a model" usefully signals that no heavy side effects occur, but it says nothing about whether the call is read-only, what permissions or environment it depends on, or how the compatibility result is reported — all behaviors the schema cannot convey since there are no parameters.

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 short sentence with the action and its key constraint front-loaded; every word earns its place and nothing is padded.

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

Completeness3/5

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

For a zero-argument diagnostic with no annotations and no output schema, the description should at least indicate the shape of the result (e.g., compatible/incompatible or a version report), since nothing else in the definition conveys return semantics. The pre-flight purpose is conveyed, but the outcome an agent should expect is left unstated.

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 standard baseline of 4 applies; there is nothing for the description to disambiguate at the parameter level.

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?

Uses a specific verb ("Check") and a specific resource ("installed DeepSeek interface compatibility"), and adds a scope qualifier ("without starting a model"). It is clear enough to act on, though the mismatch between the tool name (executor_status) and the described subject (DeepSeek interface compatibility) leaves slight ambiguity about whether this reports executor state or dependency compatibility.

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 phrase "without starting a model" implies a lightweight pre-flight/verification use case, and none of the listed siblings offer a comparable check. However, the description never states explicitly when to use it (e.g., before submitting a task) or what conditions make it unnecessary, so the guidance is only implied.

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