Skip to main content
Glama

BRAINIAC Network Exposure & Certificate Tooling

Decode X.509 certificates and flag weaknesses

network-exposure_x509-decode
Read-onlyIdempotent

Parse PEM/DER certificates and apply NIST/BR validity flags. Price $0.03 USDC. POST /api/v1/network-exposure/x509-decode. An unpaid call returns the x402 payment terms and does 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-exposure_x509-decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
nowNonow, string. Optional.
pemNopem, string, length 0 to 1000000. Optional.
derBase64NoderBase64, string, length 0 to 1000000. Optional.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
evaluatedAtNoevaluatedAt. String.
limitationsNolimitations. Array.
certificatesNocertificates. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and open-world access, so the description's contribution is the commercial and transport behavior: $0.03 USDC cost, the POST endpoint, and the fact that an unpaid call returns x402 payment terms without executing. That is genuinely useful context an agent cannot get from structured fields.

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?

Four short sentences with the capability front-loaded and the cost/endpoint/payment caveat kept compact. No filler or repetition, though the payment sentence could be tightened into one clause.

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 values need not be described, and the payment path is covered. However, all three parameters are optional, and the description never states that at least one of pem or derBase64 must be supplied for a meaningful decode — a real gap for correct invocation.

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 the baseline is 3. The description confirms the accepted encodings (PEM/DER) but says nothing about the `now` parameter or about whether pem and derBase64 are mutually exclusive, which the schema's tautological per-field descriptions also fail to clarify.

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 gives a specific verb and resource ("Parse PEM/DER certificates") plus the added outcome ("apply NIST/BR validity flags"), which is more than a restatement of the title. It does not distinguish itself from near siblings such as csr-decode-validate or tls-fingerprint-compute, so an agent must infer the boundary from the name alone.

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 named alternative among the many decode/validate siblings. The only conditional statement is about payment failure, which is a prerequisite rather than usage guidance.

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