Skip to main content
Glama
Sign In
arcane-mcp

arcane-mcp

by MikeCase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_all_vulnerabilities

Retrieve a complete inventory of all vulnerabilities across the environment to identify and address security issues.

Instructions

List all vulnerabilities across the environment.

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

Input Schema

NameRequiredDescriptionDefault
env_idNo0
agent_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations provided, so the description carries full burden. It omits behavioral traits like whether the list is paginated, real-time, or requires specific permissions, leaving the agent uncertain about side effects or performance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, concise but lacking substance. It could be improved with additional context without becoming verbose.

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?

Given no output schema and zero parameter documentation, the description is incomplete. It does not specify what the returned list contains (e.g., vulnerability IDs, severity) or how to filter by environment.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description does not explain the purpose or default values of env_id and agent_token. The agent cannot infer how to use these parameters correctly.

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 clearly states the action (list) and resource (vulnerabilities) with scope (across the environment). However, it does not differentiate from sibling tools like get_vulnerability_summary_all, which may serve a similar purpose.

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?

No guidance on when to use this tool versus alternatives such as get_vulnerability_summary_all or get_image_vulnerabilities. The agent lacks context to make an informed choice.

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