Skip to main content
Glama
GoMobSec MCP server

GoMobSec MCP server

Scan status

get_scan
Read-only

Retrieve the status of a specified mobile app security scan and, once complete, get its findings count by severity.

Instructions

Status of one scan and, once complete, its findings count by severity.

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

Input Schema

NameRequiredDescriptionDefault
scan_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior: the findings count only materializes after the scan completes, implying a partial result before then. It says nothing about rate limits, polling intervals, or error behavior for an unknown scan_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler; the conditional clause is compact and informative. Slightly terse for the information an agent needs.

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 return structure need not be spelled out, and the description correctly previews the severity breakdown. However, for a status-polling tool in a suite containing wait_for_scan and get_findings, the absence of any guidance on provenance of scan_id or when to poll versus wait leaves a meaningful hole.

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 coverage is 0%, so the description carries the full burden for the single parameter, and it says nothing about scan_id — not its format, not that it comes from list_scans or start_scan. With one required undocumented parameter, this is a real gap rather than a neutral baseline.

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 resource (one scan) plus what it returns (status and, once complete, findings count by severity), which cleanly separates it from list_scans. It does not explicitly name a sibling as an alternative, so it stops short of a 5.

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?

The phrase 'once complete' hints at polling semantics, but there is no when-to-use guidance, no mention of wait_for_scan for blocking on completion, and no note that get_findings is the tool for detailed findings. The agent must infer all routing decisions.

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