Skip to main content
Glama

smb_audit

Check SMB protocol versions and security mode settings on a target to identify outdated dialects or weak signing configuration.

Instructions

Check SMB protocol versions and security mode settings on a target.

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": {
      "target": "<target>"
    },
    "name": "smb_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full disclosure burden and does not meet it. 'Check' implies a read-only probe, but nothing states that it is non-destructive, whether authentication is needed for security-mode enumeration, or what happens on an unreachable/closed host.

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 resource and the audited attributes come first. It is economical, though the brevity is partly the source of the missing guidance rather than purely a virtue.

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 return-value documentation is not required, and the tool is simple with one parameter. However, for a network probe with zero annotations, the absence of target-format rules and connectivity/permission expectations leaves real gaps.

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% and the only guidance for the single required parameter is the phrase 'on a target'. The description does not clarify whether target accepts an IP, hostname, CIDR range, or host:port form, which is the key ambiguity for this tool.

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?

States a specific verb (Check) and resource (SMB protocol versions and security mode settings) scoped to a target. It is clearly distinguishable from ssh_audit, rdp_audit and other protocol audits by name and content, though the description never explicitly names or contrasts those siblings.

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?

There is no statement of when to use this versus alternatives such as service_scan or vuln_scan, and no prerequisites (e.g., port 445 reachability, credentials, network position) are given. An agent must infer the use case entirely from 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.