Skip to main content
Glama

Add software to a monitor

add_software
Idempotent

Adds one piece of software the website runs, by name (Debian, nginx, WordPress, Next.js…), package (npm:lodash, composer:vendor/package, pypi:django, wp-plugin:slug) or NVD product (cpe:vendor:product), with its version if known. Replaces a detected or imported entry for the same product. Free.

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": {
      "id": "<id>",
      "name": "<name>"
    },
    "name": "add_software"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMonitor ID from list_monitors.
nameYesProduct name or package, such as "Debian" or "npm:lodash".
versionNoInstalled version, such as 12 or 4.17.21. Leave out when unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, idempotent and closed-world, so the bar is lower. The description still adds real value beyond them by disclosing upsert semantics: it replaces an existing detected or imported entry for the same product, which explains why the operation is idempotent. The unexplained 'Free' and the absent description of the response are the remaining gaps.

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?

One dense, front-loaded paragraph that leads with the verb and the resource before listing formats; the parenthetical examples earn their space. The dangling 'Free.' sentence is the one piece that is terse to the point of ambiguity. No redundant restatement of the title.

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?

For a three-parameter mutation with full schema coverage, four annotations and no output schema, this covers purpose, accepted formats, version optionality and replacement behavior. Only the return value and the meaning of 'Free' are left open, which is minor given the annotation coverage.

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?

Schema coverage is 100%, so baseline is 3, but the description genuinely extends it by spelling out the accepted identifier prefixes (npm:, composer:, pypi:, wp-plugin:, cpe:vendor:product) and by noting the version is optional when unknown. That prefix vocabulary is the key thing an agent needs to form a valid name value and is only partially present in the schema.

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

Purpose4/5

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

Specific verb plus resource: 'Adds one piece of software the website runs', scoped to a monitor. It goes further than the name by enumerating the three identifier families accepted (name, package prefix, NVD cpe). It does not explicitly contrast itself with import_software or scan_website_software, so the sibling differentiation is implied by 'one piece' rather than stated.

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?

Usage is only implied: the reader infers this is the manual, single-entry path as opposed to the bulk import or scan siblings. 'Replaces a detected or imported entry for the same product' gives a useful condition for calling it, but there is no explicit when-to-use/when-not or named alternative. The trailing 'Free' hints at a cost distinction without explaining it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources