Skip to main content
Glama

diff_scans

Compare two previously run scan IDs to reveal hosts up/down and detect port and OS changes.

Instructions

Diff two previously run scans by id: hosts up/down, port and OS changes.

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": {
      "scan_id_a": "<scan_id_a>",
      "scan_id_b": "<scan_id_b>"
    },
    "name": "diff_scans"
  }
}

Input Schema

NameRequiredDescriptionDefault
scan_id_aYes
scan_id_bYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose that this is a comparison over already-completed scans and names the output facets, implying a read-only operation. It omits error behavior for invalid or mismatched ids and whether argument order (A vs B) changes the diff direction. Return shape is covered by the output schema, so that omission is acceptable.

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?

A single sentence, front-loaded with the verb and resource, followed by the enumerated comparison facets. No filler or redundant phrasing.

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 simple two-integer-parameter comparison tool with an output schema documenting the return, the description covers purpose and output facets adequately. The remaining gap is directional/baseline semantics and whether the scans must be compatible, which an agent might need in order to interpret results correctly.

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 0%, but the two parameters are self-describing integers and the description's phrase 'by id' confirms they are scan identifiers rather than names or indices. There is little additional semantics an integer pair could carry, so the gap is minor. No clarification of ordering semantics (which id is the baseline) is supplied.

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 ('Diff') and resource ('two previously run scans by id') and enumerates the comparison axes (hosts up/down, port and OS changes). It partially distinguishes itself from the sibling diff_latest by requiring explicit scan ids, but never names or contrasts that sibling.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite (e.g., both scans must exist / target the same scope), and no mention of the obvious alternative diff_latest for comparing against the newest scan. The agent must infer the selection rule entirely.

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