Skip to main content
Glama

diff_latest

Compare the two most recent scans of a target to spot changes in open ports and services. Provide the target to get a diff of the newest results.

Instructions

Diff the two most recent scans of the same target and tool.

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": {
      "target": "<target>"
    },
    "name": "diff_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden. It usefully reveals the selection logic (latest two scans, matched on both target and tool, so scan identity is derived rather than passed), but says nothing about preconditions such as behavior when fewer than two scans exist, nor about permissions or cost.

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 efficient sentence with the differentiating qualifier ('two most recent') front-loaded after the verb. Nothing is wasted.

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?

An output schema exists, so return structure need not be explained, and the operation is simple with one parameter. The only meaningful omission is the precondition of at least two prior scans and the format expected for target.

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?

One required parameter at 0% schema description coverage, so the description must carry meaning and only partially does: 'target' is glossed as the same target whose scans are compared, but the accepted format (hostname, IP, CIDR, scope name) is not specified.

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 ('Diff') plus the precise resource boundary: the two most recent scans of the same target and tool. The 'most recent' qualifier implicitly separates it from diff_scans, which presumably takes explicit scan identifiers, though it never names that alternative.

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 agent can infer this is the shortcut for comparing the newest two scans without supplying scan IDs. There is no explicit when-to-use/when-not statement and no reference to diff_scans as the alternative for arbitrary scan pairs.

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