Skip to main content
Glama

mcp-audit

scan_mcp_server

审计一个 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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Because no annotations are provided, the description must disclose behavior on its own. It says nothing beyond 'returns a structured risk list': it does not say whether the scan is read-only, whether it executes or launches the target MCP server, whether it modifies the project, permission requirements, or how long the operation takes. For a security-scanning tool, these omissions matter because an agent cannot tell whether the operation has side effects.

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?

It is a single front-loaded sentence with no filler, and the purpose statement comes first with a return hint after it. It is efficient, though its brevity reflects under-specification rather than disciplined economy.

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 the return values need not be described, and the purpose is covered. However, given that this tool has no annotations and has an undocumented boolean parameter, the description is thinner than the tool's complexity warrants; it leaves behavior and the include_tests behavior unaddressed.

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 description coverage is 0%, so the description must supply meaning for both parameters, but '本地路径' only clarifies that the path parameter points to a local project. The include_tests parameter (default false) is never mentioned, so an agent gets no guidance on when to enable it or what it changes in the scan scope.

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 (audit), an object (an MCP server project at a local path), and a scope (security risks), plus a note about the structured risk list. That is enough for an agent to tell what the tool does. Differentiation from other tools is not required, because the sibling list is empty. Only minor ambiguity remains about what kinds of risks are covered.

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 description only implies that the tool works on local projects (through '本地路径'), and it gives no explicit guidance on when to use this tool versus when not to, nor any prerequisites such as whether the path must exist or be a project root. For an agent, the trigger conditions must be inferred entirely from the name and the one-line purpose.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources