Skip to main content
Glama
Sign In
Security Scanner MCP Server

Security Scanner MCP Server

by friendlygeorge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_version

Read-only

Retrieve version information for Trivy and Grype to confirm installed security scanning engines.

Instructions

Get version information for installed security scanning engines (Trivy and/or Grype).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so description adds value by specifying target engines (Trivy/Grype) and confirming it's a version check. However, it doesn't disclose what actions it does NOT perform (like scanning or updating), which would be helpful.

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?

Single, concise sentence that efficiently communicates the tool's purpose. Every word is relevant, no redundancy or extraneous information.

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?

Given no output schema, description could specify the format of returned version info (e.g., individual version strings per engine). Lacks this detail but still conveys core purpose adequately for a simple tool.

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?

No parameters exist, so baseline is 4 per guidelines. Description correctly doesn't add parameter info as there are none. Schema coverage is effectively complete since schema is empty.

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?

Description explicitly states it retrieves version information for installed security scanning engines, naming Trivy and/or Grype. This clearly identifies the tool's action and scope, differentiating it from sibling tools that perform scans or other operations.

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?

No explicit guidance on when to use or avoid this tool versus alternatives. While the purpose is clear, the description does not indicate prerequisites or contexts (e.g., checking engine availability before scanning), leaving reliance on implicit understanding.

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