Skip to main content
Glama

get_scan_report

Retrieve a previous scan report as JSON (all clauses, quotes, scores).

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": "<scan_id>"
    },
    "name": "get_scan_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
scan_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden; 'Retrieve' implies a read-only operation and it discloses the report's contents. However, it says nothing about permissions, whether old reports expire or are retained, or what happens for an unknown scan_id — gaps an agent would care about for a fetch-by-id tool.

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, front-loaded with the verb and resource, with the parenthetical payload detail doing real work. Nothing is padded or repeated from the title.

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?

An output schema exists, so the description need not explain return values, and it briefly characterizes them anyway. The remaining hole is input-side: how to get a valid scan_id and whether reports are always retrievable is left unaddressed, which matters for a lookup tool with zero schema documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, with only a bare 'Scan Id' title, so the description must compensate — but it never explains what a scan_id is or where to obtain one. The single parameter is effectively undocumented in both places.

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?

Uses a specific verb and resource ('Retrieve a previous scan report') and names the payload contents (all clauses, quotes, scores), which separates it from scan-creating siblings like scan_terms_of_service. It does not explicitly name any sibling, so differentiation is inferred from the word 'previous' rather than stated.

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' implies this is for fetching an already-completed scan rather than starting one, which is useful implied context. But there is no explicit when-to-use/when-not statement, no mention of how a scan_id is obtained, and no routing to compare_scans or batch_scan_terms for adjacent needs.

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.