Skip to main content
Glama

Remove software from a monitor

remove_software
DestructiveIdempotent

Removes an entry from get_vulnerabilities' software list. Software the scan found is ignored instead, so the next scan does not add it back. 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>",
      "software_id": "<software_id>"
    },
    "name": "remove_software"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMonitor ID from list_monitors.
software_idYesThe entry's id from get_vulnerabilities.

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 cover the mutation profile (destructive, idempotent, not read-only), so the description earns credit for adding behavior they cannot express: scan-discovered software is ignored rather than deleted, so the next scan will not re-add it. The brevity of 'Free' adds pricing context but is terse. It stops short of stating failure behavior for an unknown software_id or what happens to already-open vulnerabilities.

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?

Three short, front-loaded sentences: what it removes, the side effect that matters most, then cost. Nothing is padded, although the one-word 'Free' sentence reads a little telegraphic.

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?

For a two-parameter idempotent mutation with full schema coverage and rich annotations, the description covers the one non-obvious consequence (scan results ignored so entries do not return). No output schema exists, so return values need no explanation, and nothing essential to calling it correctly is missing.

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 coverage is 100% and both parameters already point to their source (monitor ID from list_monitors, entry ID from get_vulnerabilities), so the schema carries the semantic load. The description adds no further meaning about the ID pair beyond reinforcing the get_vulnerabilities link.

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?

States a specific verb (removes) and a precise resource: an entry on get_vulnerabilities' software list for a monitor. The title plus the reference to the vulnerability software list make it distinguishable from add_software, import_software, and delete_monitor, though the description never names those siblings directly.

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 implied by the effect described (removing a tracked software entry and preventing re-addition on the next scan), which tells an agent this is the right call for pruning a monitor's list. It does not explicitly contrast with add_software or import_software, nor mention prerequisites such as needing the entry to already exist.

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