Skip to main content
Glama

AutoPay

security_scan_tls

TLS certificate check (passive only): certificate trust, issuer, SAN, expiry, negotiated TLS version; score + grade. $0.002; synchronous, charged only on success. Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key.

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

Input Schema

NameRequiredDescriptionDefault
urlNoSite URL, e.g. https://example.com
domainNoAlternative to url: bare domain, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses that the scan is passive (no active probing), synchronous rather than job-based, priced at $0.002, and billed only on success. It also names the two auth mechanisms (X-PAYMENT x402 USDC on Base, or a prepaid API key) with the exact header name. It stops short of rate limits, failure/refund behavior, or what the score/grade scale means.

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?

Three compact clauses: what is checked, cost/latency/billing, then payment. It is front-loaded with the capability and every clause carries actionable information — no filler or restated title text.

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

Completeness4/5

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

For a two-optional-parameter read tool with no output schema, the definition covers capability, output shape at a high level (score + grade), cost, sync semantics, and auth. The one meaningful omission is the input requirement rule — with 0 required parameters, the agent is not told that at least one of url or domain must be given, nor what error results otherwise.

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 coverage is 100%, so both parameters are already documented with examples, and the description adds no further meaning about url vs. domain or their relationship. Baseline 3 applies since the schema does the heavy lifting. Notably, the definition leaves unaddressed the fact that zero parameters are required when presumably one of url/domain must be supplied.

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 names a specific verb-and-resource ('TLS certificate check') and enumerates exactly what is inspected: trust, issuer, SAN, expiry and negotiated TLS version, plus a score and grade. Combined with the 'passive only' scope, this functionally separates it from siblings like security_scan_dns or security_scan_headers, though it never names an alternative explicitly.

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 certificate/TLS questions, and 'passive only' signals a non-intrusive check. There is no explicit guidance on when to prefer security_scan_full or security_scan over this narrower check, and no stated preconditions.

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