Skip to main content
Glama

get_instance_scan_summary

Read-only

Summarizes latest Instance Scan results with scores, findings by category, priority, check, table, and application, trends, remediation guidance, and AI/agent coverage to guide remediation.

Instructions

Summarise the latest Instance Scan results: each saved scan with its latest and previous run and scores, findings grouped by category, priority, check, table and application, trend per check against the previous run, remediation guidance for the top checks, and coverage of AI and agent checks

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_instance_scan_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
asyncNoRun as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.
resultNoSummarise one scan result (sys_id, number or CI/CD progress id) instead of the latest run of every saved scan
categoriesNoComma list of categories to report: security, performance, upgradability, manageability, user_experience (default all)
top_checksNoHow many checks to list with remediation (default 25)
max_resultsNoHow many scan results to analyse in depth (default 6)
samples_per_checkNoSample findings per top check (default 2, 0 to skip)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds real value by disclosing the shape of what is returned (per-scan latest vs previous runs, trend deltas, top-check remediation, AI/agent coverage). It does not mention the long-running auto-switch to a background job, but that is documented on the async parameter.

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?

One sentence, purpose front-loaded before the colon, then a dense enumeration of output sections with no filler or repeated phrasing. Long but every clause earns its place by describing a distinct part of the result.

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, so the description carries the burden of describing returns, which it does thoroughly. Combined with a fully documented 6-parameter schema and read-only annotations, an agent has nearly everything it needs; only explicit sibling routing and any performance/cost caveats are 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 description coverage is 100%, so all six parameters are already documented with defaults and meaning. The description only indirectly maps to them ('grouped by category', 'remediation guidance for the top checks'), adding no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 opens with a specific verb and resource ('Summarise the latest Instance Scan results') and then enumerates exactly what the summary contains: latest/previous runs, scores, grouped findings, trends, remediation and AI/agent coverage. That clearly separates it from get_instance_scan_findings and run_instance_scan in spirit, though it never names those siblings explicitly.

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 explicit when-to-use or when-not-to-use guidance. The agent must infer that this is the aggregate/overview tool and that get_instance_scan_findings is the drill-down tool; the only routing hint ('instead of the latest run of every saved scan') lives in the result parameter's schema description, not in the tool description.

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

Deploy Server

Other Tools