Skip to main content
Glama
Sign In
MCP Configurator Server

MCP Configurator Server

by Dheeraj32903
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

validate_command

Check if a command executable exists on the system path or as an absolute path. Returns availability status.

Instructions

Checks whether a command executable exists on the system path or as an absolute path.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "command": "<command>"
    },
    "name": "validate_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYesExecutable name (e.g. node, npx) or absolute path to check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description must disclose all behavioral traits. It states the check is for existence, but does not indicate the return format (e.g., boolean, status code), or what happens on success/failure. This is insufficient for an agent to predict the tool's behavior.

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?

The description is a single, concise sentence that front-loads the purpose. However, it is very brief and could benefit from structured format, but it has no wasted words.

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

Completeness2/5

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

Given the simple nature and one parameter, the description omits critical details about the return value (e.g., boolean, error) and behavior. An agent cannot fully understand what to expect from the tool's output, making it incomplete.

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% for the single parameter 'command'. The tool description adds no new meaning beyond what the schema already provides ('Executable name ... or absolute path'). Baseline of 3 is appropriate.

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?

The description clearly states the tool checks existence of a command executable on the system path or absolute path. This specific verb+resource distinguishes it from sibling tools like get_config and list_backups, which have different purposes.

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?

The description provides no guidance on when to use this tool or when not to. No alternatives or exclusions are mentioned, leaving the agent to infer context.

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