Skip to main content
Glama

BRAINIAC Network Exposure & Certificate Tooling

Compute JA3 and JA4 TLS fingerprints

network-exposure_tls-fingerprint-compute
Read-onlyIdempotent

Derive JA3/JA4 from ClientHello fields without capturing traffic. Price $0.03 USDC. POST /api/v1/network-exposure/tls-fingerprint-compute. 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_tls-fingerprint-compute"
  }
}

Input Schema

NameRequiredDescriptionDefault
alpnNoalpn, array. Optional.
ciphersNociphers, array. Optional.
transportNotransport, string, one of tcp, quic, dtls. Required.tcp
extensionsNoextensions, array. Optional.
legacyVersionNolegacyVersion, integer, from -9007199254740991 to 9007199254740991. Optional.
clientHelloHexNoclientHelloHex, string, length 0 to 32768. Optional.
ecPointFormatsNoecPointFormats, array. Optional.
supportedGroupsNosupportedGroups, array. Optional.
supportedVersionsNosupportedVersions, array. Optional.
signatureAlgorithmsNosignatureAlgorithms, array. Optional.

Output Schema

NameRequiredDescriptionDefault
ja3Noja3. String.
ja4Noja4. String.
ja4_rNoja4_r. String.
sourcesNosources. Array.
ja3StringNoja3String. String.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the exact endpoint, a $0.03 USDC price, and the x402 rule that an unpaid call returns payment terms and does not execute. It does not cover rate limits or result caching, so not a 5.

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, front-loaded with the purpose before price, endpoint and payment behavior. Every sentence carries information; only the raw method/path line is arguably redundant with the tool name, keeping it from a 5.

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 explained, and the payment behavior is disclosed. But for a tool with 10 optional parameters where the central question is whether to pass clientHelloHex or the structured fields, that guidance is missing, which is a meaningful completeness gap.

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%, so the baseline is 3. The description adds top-level meaning ("from ClientHello fields"), but does not explain the relationship between clientHelloHex and the ten decomposed fields, nor which combinations are valid or preferred, leaving the most consequential invocation decision undocumented.

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?

"Derive JA3/JA4 from ClientHello fields without capturing traffic" names a specific verb (derive), a specific artifact (JA3/JA4 TLS fingerprints), and the input source, which distinguishes it from a passive-capture approach. It does not explicitly differentiate itself from the sibling fingerprint tools such as network-exposure_service-banner-fingerprint, so it falls short of a 5.

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 phrase "without capturing traffic" implies this is the tool to use when you already have ClientHello data rather than a packet capture, which is a form of implied usage guidance. However, there is no explicit when-to-use/when-not-to-use statement and no routing to any sibling tool.

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