Skip to main content
Glama

BRAINIAC Telecom & Network Infrastructure Intelligence

Inventory TLS certificate expiry

network-intelligence_certificate-expiry-inventory

Inventory caller-supplied TLS certificate expiry dates, or optionally inspect a public hostname on port 443 only. Price $0.03 USDC. POST /api/v1/network-intelligence/certificate-expiry-inventory. Unpaid calls return 402 and do not run.

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": "network-intelligence_certificate-expiry-inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
logsNo
textNo
filesNo
configsNo
bgpRoutesNo
incidentsNo
publicDnsNo
publicTlsNo
dnsRecordsNo
reputationsNo
certificatesNo
latencySamplesNo
latencyAnomalyZNo
expiryWarningDaysNo
packetLossSamplesNo
packetLossWarnPctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It usefully states the price, POST endpoint, 402 unpaid behavior, and port-443 limitation, but it omits authentication requirements, read-only semantics, return behavior, and other operational limits for a complex 20-parameter tool.

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?

The description is three sentences, front-loaded, and free of filler. The price, payment behavior, and endpoint details are useful, though the HTTP endpoint is somewhat implementation-specific.

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

Completeness1/5

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

For a 20-parameter tool with nested objects, no annotations, no output schema, and 0% schema description coverage, the description is far too thin. It does not give an agent enough information to call the tool correctly or understand the accepted input formats.

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 coverage is 0% across 20 parameters. The description loosely maps to caller-supplied certificate data and public hostname inspection, but it does not explain asOf, expiryWarningDays, csv/json/text/file inputs, or the many nested arrays such as certificates, publicTls, logs, and dnsRecords.

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 states a specific verb and resource: inventory TLS certificate expiry dates. It distinguishes caller-supplied certificate data from optional public hostname inspection on port 443, which clearly identifies the tool’s core function.

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 definition implies two usage modes: caller-supplied certificate data or optional inspection of a public hostname. However, it does not explicitly say when to use this tool versus alternatives, nor does it provide prerequisites or exclusions beyond the port-443 restriction.

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