Skip to main content
Glama

compare_scans

Compare 2-20 previous scans: vendor ranking plus a category-by-category matrix of worst severity per vendor. Free — uses already-paid-for scans.

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_ids": "<scan_ids>"
    },
    "name": "compare_scans"
  }
}

Input Schema

NameRequiredDescriptionDefault
scan_idsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose two meaningful traits: the 2-20 input bound and that the operation is free because it reuses prior scans. It says nothing about behavior on invalid or mismatched scan IDs, whether scans must share the same terms/site to be comparable, or whether any scans get mutated.

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?

Two short clauses, front-loaded with the purpose and cardinality, followed by the cost note. Every phrase carries information and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema exists, so return values needn't be spelled out, and the description still summarizes them briefly. For a read-only comparison tool with no annotations, the notable missing piece is the comparability precondition (scans of the same terms/subject) and what happens when invalid IDs are supplied.

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?

The single parameter has 0% schema description coverage, so the description must compensate; it does add the important '2-20' cardinality constraint and the fact that IDs must refer to previous scans. It still omits the ID format and where the agent obtains valid scan IDs (e.g., from a scan or report call).

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?

The description uses a specific verb ('Compare') plus a specific resource ('2-20 previous scans') and even states the output shape: vendor ranking plus a category-by-category severity matrix. It implicitly separates itself from get_scan_report (single-scan reporting), but it never names that sibling explicitly.

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?

'Previous scans' and 'uses already-paid-for scans' imply the tool applies only when scans have already been run and hints that it costs no quota, which is useful context for choosing it over rescanning. However, there is no explicit statement of when to use this instead of get_scan_report or when-not to use it (e.g., scans that are not comparable).

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.