Skip to main content
Glama

scan_mcp_server

Audit a local MCP server project for security risks and return a structured risk list before connecting it to your agent.

Instructions

审计一个 MCP server 项目(本地路径)的安全风险,返回结构化风险清单

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": {
      "path": "<path>"
    },
    "name": "scan_mcp_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes要扫描的本地文件或目录的绝对路径
include_testsNo是否同时扫描测试/fixture 文件

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses almost nothing beyond the fact that a risk list comes back. It does not say whether the scan is read-only, whether it executes or imports project code, what permissions or prerequisites are needed, or how broad the risk coverage is.

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 purpose, input, and return value, and no wasted wording. It is efficient but so terse that it borders on under-specification rather than true concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description is the only source of behavioral and return-value context, and it names neither the risk categories produced nor the read-only/side-effect profile. For a security-audit tool that will presumably read and possibly execute project files, that leaves an agent without key facts.

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 both 'path' and 'include_tests' are already documented in the schema. The description only reinforces that the path is local, adding no format, default, or effect information beyond the structured fields.

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?

Specifies the verb (security audit/scan), the resource (an MCP server project at a local path), and the output shape (a structured risk list). The 'local path' phrasing implicitly separates it from scan_public_repo, but the contrast is never stated outright.

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?

Usage is only implied: an agent can infer this is the tool for locally-cloned MCP server projects. There is no explicit when-to-use, when-not-to-use, or reference to the sibling scan_public_repo for remote repositories.

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