Skip to main content
Glama
Sign In

QualityMax Cloud

by io.qualitymax.app
OverviewDiscussionsAdmin

Get Dependency & CVE Scan

get_dependency_scan
Read-only

Read your dependency scan status and a page of findings. Free Beta Plus or Studio+ required; reports expire after 24 hours. Poll queued/running scans no more often than every two seconds. For completed scans follow next_offset until null to read every finding. Failed scans have no security verdict.

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_dependency_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum findings per page.
offsetNoFinding offset from next_offset.
contextNoExplain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
scan_idYesID returned by start_dependency_scan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare a safe read, and the description adds substantial context beyond them: entitlement gating, a 24-hour report expiry, a rate-limit-style polling floor, and the fact that failed scans return no security verdict. These are exactly the traits an agent needs to avoid misinterpreting an empty or partial result.

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?

Five short sentences, every one carrying a distinct operational fact, with the core purpose front-loaded before the entitlement, expiry, polling, and pagination constraints. No filler or restatement of the title.

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?

No output schema exists, and the description compensates well by describing the returned status, paged findings, next_offset continuation, and the failed-scan case. It stops short of describing the failure status values an agent would need to branch on, so it is strong but not exhaustive.

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 coverage is 100%, so the schema already documents limit, offset, context, and scan_id, which sets the baseline at 3. The description adds one genuinely useful detail: that offset should be driven by the previous response's next_offset and consumed until null, linking the parameter to a return value the schema cannot express. No other parameter meaning is added.

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 and resource: 'Read your dependency scan status and a page of findings.' That is clearly distinct from the sibling start_dependency_scan, which initiates rather than reads a scan. It never names the sibling explicitly, so sibling differentiation is inferred 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 Guidelines4/5

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

Gives concrete operational conditions: plan entitlement ('Free Beta Plus or Studio+ required'), a polling cadence ('no more often than every two seconds'), and a termination rule for pagination ('follow next_offset until null'). It does not explicitly route the agent to start_dependency_scan when no scan exists or to another tool when the report has expired, so alternatives remain unstated.

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

All QualityMax Cloud toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources