Skip to main content
Glama

security-crypto

x509_certificate_inspect

Inspect an X.509 PEM/DER TLS certificate using Node crypto.X509Certificate for subject, issuer, SANs, expiry, fingerprint256, and key type.

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

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo
base64DataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the underlying implementation (Node crypto.X509Certificate) and enumerates the fields surfaced, which implicitly signals a non-destructive parse, but it says nothing about error behavior for malformed certificates, whether expired certs are rejected, or any size/permission constraints.

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 that packs verb, resource, encodings, implementation and returned fields with no filler. It is dense but every clause adds information an agent needs.

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 description partly compensates for the missing output schema by enumerating the returned attributes, which is genuinely useful. However, with three undocumented input parameters and no annotations, the tool definition is silent on how to supply input and on failure modes, leaving a real gap for a caller.

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% and all three parameters (text, filePath, base64Data) are undocumented and optional, yet the description never explains these mutually exclusive input modes or which takes precedence. Only the 'PEM/DER' mention hints at accepted content, leaving the most consequential choice for the caller unexplained.

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 (Inspect) and resource (X.509 PEM/DER TLS certificate), plus the exact attributes it extracts (subject, issuer, SANs, expiry, fingerprint256, key type). This clearly distinguishes it from siblings like pgp_packet_inspect or saml_assertion_decode, though it never names or contrasts those alternatives.

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 when-to-use or when-not-to-use guidance, and no mention of prerequisites such as certificate validity or input source selection. The agent is left to infer that this is a read-only parse of a certificate blob versus other crypto inspection tools.

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