Skip to main content
Glama
Sign In
Security Scanner MCP Server

Security Scanner MCP Server

by friendlygeorge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

update_db

Update the vulnerability database to ensure scans use the latest security data. Run before scanning if the database is outdated.

Instructions

Update Grype's vulnerability database to the latest version. Recommended before scanning if the DB hasn't been updated recently.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior3/5

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

Annotations (readOnlyHint: false, openWorldHint: false) indicate a mutating operation, and the description confirms this. However, it does not disclose potential side effects, network requirements, or failure modes beyond what is implied.

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?

Two sentences, front-loaded with the action, no extraneous words. Efficient and easy to parse.

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

Completeness5/5

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

The description is fully sufficient for a parameterless tool with no output schema. It covers purpose and usage context adequately.

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?

With zero parameters, the description need not add parameter information. Baseline of 4 is appropriate as no param details are missing.

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 specific action ('Update Grype's vulnerability database') and the resource ('latest version'), clearly differentiating it from sibling tools like db_status or scan operations.

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

Usage Guidelines4/5

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

Provides clear usage guidance by recommending this tool before scanning if the database hasn't been updated recently. Lacks explicit when-not-to-use or alternatives, but is sufficient for a simple tool.

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