Skip to main content
Glama
GoMobSec MCP server

GoMobSec MCP server

Scan findings

get_findings
Read-only

Retrieves findings from a completed mobile app security scan, ordered by severity with CWE, MASVS, CVSS, location, and description; optionally filters by severity and includes false positives.

Instructions

Findings of a completed scan: severity, title, CWE, MASVS category, CVSS, location and description, most severe first. Optionally filter by severity. False positives are left out unless include_false_positives is true.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
scan_idYes
severityNo
include_false_positivesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 the description is not carrying the safety burden. It still adds real behavioral detail beyond them: results are ordered most-severe-first, and false positives are excluded unless include_false_positives is true. It does not mention truncation or result-size limits, which keeps it from a 5.

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 dense sentences, front-loaded with what is returned and immediately followed by the filtering behavior. Every clause (field list, ordering, severity filter, false-positive default) carries information an agent needs, with no filler.

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 the description needn't detail return values, yet listing the key fields is a helpful preview. For a four-parameter read tool with annotations, the only real gap is the undocumented limit/pagination behavior.

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 0%, so the description must carry parameter meaning, and it does explain severity as an optional filter and clarifies the default semantics of include_false_positives. The limit parameter (default 50) is never mentioned, leaving the agent unaware of truncation or pagination behavior for a potentially large finding set.

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 names a specific resource (findings of a completed scan) and enumerates the returned fields (severity, title, CWE, MASVS, CVSS, location, description), which clearly separates it from get_scan or list_scans. It lacks an explicit verb ("List"/"Retrieve") and never names a sibling tool, so it stops short of the top mark.

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?

"Completed scan" implies the scan must have finished, which usefully steers an agent toward wait_for_scan first, and the severity filter plus the false-positive default are stated. However, there is no explicit when-to-use versus alternatives such as download_report for full reports, and no stated behavior when the scan is still running.

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