Skip to main content
Glama

Scan installed agent setup

scan_installed
Read-onlyIdempotent

Audits installed AI agent configurations and project files to surface security findings using read-only, offline checks.

Instructions

Scans the agent setup already on this machine, like toolmoat scan with no paths: Claude Code skills, plugins, commands, agents, hooks, settings and user config, Claude Desktop, Cursor, VS Code, Windsurf, Codex and Gemini CLI configs, plus the project files of the server working directory. Read-only and offline.

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

Input Schema

NameRequiredDescriptionDefault
deepNoAlso walk node_modules, virtualenvs and caches.
max_findingsNoLargest number of findings to return, most severe first.
min_severityNoLeave out findings below this severity.low

Output Schema

NameRequiredDescriptionDefault
toolYes
countsYes
skippedYes
targetsYes
versionYes
completeYesFalse when some files or folders were not scanned; a scan that is not complete is not a clean result.
findingsYes
filesScannedYes
skippedFilesYes
highestSeverityYes
omittedFindingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.1
    • addedOutput schema / properties / complete
      Added value: +{
      +  "description": "False when some files or folders were not scanned; a scan that is not complete is not a clean result.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / skipped
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "path": {
      +        "type": "string"
      +      },
      +      "reason": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "path",
      +      "reason"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "tool",
      -  "version",
      -  "filesScanned",
      -  "targets",
      -  "counts",
      -  "highestSeverity",
      -  "findings",
      -  "omittedFindings",
      -  "skippedFiles"
      -]New value: +[
      +  "tool",
      +  "version",
      +  "filesScanned",
      +  "targets",
      +  "counts",
      +  "highestSeverity",
      +  "findings",
      +  "omittedFindings",
      +  "skippedFiles",
      +  "complete",
      +  "skipped"
      +]
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=true, so 'Read-only and offline' largely restates structured data. The description does add useful scope context (project files of the working directory included), but says nothing about cost, performance, or what a finding looks like.

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?

A single front-loaded sentence with no filler; the long enumeration is dense but each item earns its place by defining scan scope. Slightly list-heavy but well structured.

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 return values need no explanation, and the description fully covers what is scanned and the read-only/offline contract. What remains unaddressed (how findings are ordered or scoped by the parameters) is handled by the schema.

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 100%, so all three parameters (deep, max_findings, min_severity) are already documented. The description adds no parameter guidance beyond what the schema provides, which is the expected baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Scans') and resource ('agent setup already on this machine'), then enumerates the concrete surfaces covered (Claude Code skills, plugins, Cursor, VS Code, etc.). It is clearly distinguishable from scan_path and scan_text, which take explicit inputs.

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?

The analogy 'like `toolmoat scan` with no paths' and the enumeration of what is auto-discovered make clear this is the no-input discovery entry point versus scan_path. It lacks an explicit 'use X instead when...' exclusion, so it stops short of a 5.

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

Deploy Server

Other Tools