Skip to main content
Glama

Mark a vulnerability fixed

mark_vulnerability_fixed
Idempotent

Records that the software behind a finding from get_vulnerabilities was upgraded: to version, or by default to the first version that fixes it (the finding's fix_version). The monitor is checked again; findings that no longer apply disappear, and one that still applies stays, marked with the version. Only records the version; it does not change the server. 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>",
      "finding_id": "<finding_id>"
    },
    "name": "mark_vulnerability_fixed"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMonitor ID from list_monitors.
versionNoThe version installed. Leave out for the first version that fixes it.
finding_idYesThe finding's id from get_vulnerabilities.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by explaining that the monitor is re-checked, that resolved findings disappear while still-applicable ones persist marked with the version, and that the call only records the version without changing the server. The 'Free' note adds cost context no annotation carries, and the non-mutating intent is consistent with destructiveHint=false.

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 front-loaded sentences that put the effect and default behavior first, followed by consequences and the scope caveat. The trailing 'Free.' fragment is terse but informative rather than wasteful.

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?

There is no output schema, and the description compensates by describing the observable result in the findings list. Only the exact return payload of the call itself is left implicit, which is a minor gap for a small three-parameter tool.

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 already documents all three parameters, including the omit-version default. The description restates the default and names fix_version, adding only marginal meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and effect ('Records that the software behind a finding... was upgraded') tied to a named sibling source, get_vulnerabilities. An agent can tell immediately what changes in the system and where the inputs come from.

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?

Gives clear context for use: after upgrading the software behind a finding, and points to get_vulnerabilities for finding_id and list_monitors for the monitor id. It does not name an alternative or state when not to use it, but the situation is unambiguous.

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