Skip to main content
Glama
Sign In
Bug Bounty Assistant MCP

Bug Bounty Assistant MCP

by rohitprasad-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

ssl_scan

Check TLS/SSL certificate validity, certificate chain, protocol versions, and cipher suites for a target domain.

Instructions

Checks TLS/SSL certificate validity, chain, protocol versions, and cipher suites

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": "ssl_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesThe target domain/hostname

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

In the absence of annotations, the description carries the full burden. It states what is checked but does not disclose behavioral traits like network requirements, safety (read-only), or potential time consumption.

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?

The description is a single, well-formed sentence with no wasted words, front-loading the action and scope.

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?

The tool has no output schema, and the description does not explain the return format or error behavior. Given the simplicity, some guidance on output would improve completeness.

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% for the single parameter 'target'. The description adds context about the tool's purpose but does not clarify parameter format (e.g., protocol requirement, IP vs hostname). Baseline 3 is appropriate.

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?

The description specifies the verb 'Checks' and the resource 'TLS/SSL certificate validity, chain, protocol versions, and cipher suites', clearly distinguishing it from sibling tools like analyze_cookies or check_security_headers.

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 description implies usage (e.g., for SSL health checks) but provides no explicit guidance on when to use or not use it, nor does it mention alternatives among sibling tools.

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