Skip to main content
Glama
Sign In
Cybersec Toolkit

Cybersec Toolkit

by 26zl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

check_installed

Read-onlyIdempotent

Verify whether a specific cybersecurity tool is installed locally or on a remote host via SSH, using multiple detection methods to confirm availability before execution.

Instructions

Check if a specific cybersecurity tool is installed on the system.

Uses six detection strategies: .versions tracking, PATH lookup, binary-name fallback, git clone directory, run_script venv, and docker image.

When host is provided, checks installation on the remote host via SSH using 'which '.

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": {
      "tool_name": "<tool_name>"
    },
    "name": "check_installed"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoOptional remote host name (as configured via manage_remote_hosts).
tool_nameYesName of the tool to check (as listed in tools_config.json).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the bar is lower, and the description adds real context: the six ordered detection strategies and the fact that a provided host switches execution to SSH with 'which <binary>'. It stops short of saying what the response contains or what happens when detection is ambiguous.

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?

Purpose is front-loaded in one sentence, followed by the mechanism list and the remote-host branch. The strategy enumeration is slightly listy but each item carries information; nothing is redundant.

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?

With a full schema and an output schema present, the description needn't explain return values, and it covers both local and remote execution paths adequately. Only the lack of guidance on selecting this tool over its siblings leaves a small gap.

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%, so both parameters are already documented. The description adds marginal meaning by explaining that host triggers a different remote mechanism, but it doesn't elaborate on tool_name matching rules or host formatting beyond what manage_remote_hosts already implies. Baseline 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 opens with a specific verb and resource ('Check if a specific cybersecurity tool is installed'), which is immediately distinguishable from siblings like run_tool, recommend_install, and get_tool_info. The enumerated detection strategies further pin down what 'check' actually means here.

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?

It documents the conditional behavior when host is supplied (remote SSH check) but never states when an agent should call this versus reach for get_tool_info or list_tools, nor any prerequisite like registering a host first. Usage is implied rather than prescribed.

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