Skip to main content
Glama
GoMobSec MCP server

GoMobSec MCP server

List scans

list_scans
Read-only

Retrieve recent security scans for the account, newest first, with an optional 1-50 limit to review Android and iOS app findings.

Instructions

List the account's most recent scans, newest first (1-50).

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety and scope are covered. The description adds only the sort order and the limit range; it says nothing about what happens with no scans, whether results are cached, or how the open-world account scope affects results.

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?

A single sentence with no filler, and the scoping constraint ('most recent ... newest first') is front-loaded before the limit range. Nothing is redundant.

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?

One optional parameter, an output schema, and read-only annotations make this a simple tool, and the description covers scope, ordering, and limit bounds adequately. The only missing piece an agent would want is the default page size of 10 when limit is omitted.

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

Parameters4/5

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

Schema coverage is 0% — the limit property has no description, no minimum, and no maximum in the schema. The description's '(1-50)' supplies the valid bounds that the schema omits, which is real added value. It does not state the default of 10, so it does not fully compensate for the coverage gap.

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 gives a specific verb (list) and resource (the account's most recent scans), plus ordering ('newest first'), which distinguishes it from the singular get_scan sibling. It stops short of naming that sibling explicitly, but 'list ... scans' versus 'get_scan' is unambiguous.

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?

'Most recent scans' implies the usage context (browsing recent activity rather than fetching a known scan), but there is no explicit when-to-use statement, no exclusion of get_scan for single-scan retrieval, and no mention of whether pagination or a different tool is needed for older scans.

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