Skip to main content
Glama
Sign In
said-done

said-done

by Jimmy2004
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

test_executor

Detect and run local preflight checks to validate said-done execution setup without invoking an executor CLI.

Instructions

Detect and run local preflight only; never invoke an executor CLI.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose one genuinely useful behavioral fact — that this performs a local preflight and does not shell out to an executor CLI — which prevents a wrong assumption about side effects. However, it says nothing about whether the check is read-only, what permissions or local prerequisites are required, or what the result contains.

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 short sentence with the operational constraint front-loaded and no filler. It is efficient, though the terseness contributes to the ambiguity about what 'preflight' covers.

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-parameter, no-output-schema tool, the description should at least sketch what a successful preflight result indicates and how it relates to configure_executor. The critical constraint is present, but an agent cannot predict the outcome or decide confidently between this and its siblings.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. Schema coverage is 100% and the empty argument object is self-explanatory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a verb ('Detect and run') with a vague object ('local preflight'), so an agent still cannot say concretely what is being detected or tested. The negative clause 'never invoke an executor CLI' does differentiate it from an execution tool, but the core purpose of test_executor relative to siblings like list_executors or configure_executor remains unclear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is a single exclusion ('never invoke an executor CLI') but no positive guidance about when to call this versus list_executors, configure_executor, or probe_api. The agent must infer the use case from the tool name alone.

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