Skip to main content
Glama

scan_client_configs

Read-onlyIdempotent

Discover all MCP servers configured in local AI clients like Claude Desktop, Cursor and VS Code, and flag security risks such as hardcoded API keys, root directory mounts and shell wrappers.

Instructions

Scan local AI client configurations (Claude Desktop, Cursor, VS Code, Windsurf, Zed) to discover all configured MCP servers and detect security risks (hardcoded API keys/tokens, over-privileged root/home directory mounts, shell command wrappers).

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

Input Schema

NameRequiredDescriptionDefault
custom_config_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds real substance on top: which five client products are inspected and what categories of risk are detected. It still omits practical behavior like what happens when a client isn't installed, how findings are ranked, or whether unreadable configs are skipped.

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 front-loaded sentence: verb and resource first, then target list, then detection scope. No filler, no restatement of the title, and the parenthetical client list is genuinely informative rather than padding.

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?

Output schema exists, so return contents needn't be described, and annotations cover the safety profile. The remaining gap is the sole parameter, which is never mentioned, leaving the description incomplete for an agent that may want to point the scan at a non-standard location.

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

Parameters5/5

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

Placeholder

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 ('Scan') plus a precise resource ('local AI client configurations'), enumerates the five clients covered, and lists the exact findings produced (hardcoded keys/tokens, root/home mounts, shell wrappers). An agent can tell immediately that this is a read-only discovery/security tool, distinct from audit_server and inspect_manifest.

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?

The use case is implied clearly enough (discover configured MCP servers and surface security risks across local clients), but there is no explicit 'use this when...' or 'use X instead when...' guidance and no mention of prerequisites such as needing filesystem access to client config directories.

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