Skip to main content
Glama

BRAINIAC Network Exposure & Certificate Tooling

Build and verify a certificate chain offline

network-exposure_certificate-chain-build
Read-onlyIdempotent

Chain certificates against the vendored Mozilla root store. Price $0.04 USDC. POST /api/v1/network-exposure/certificate-chain-build. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "certificates": "<certificates>"
    },
    "name": "network-exposure_certificate-chain-build"
  }
}

Input Schema

NameRequiredDescriptionDefault
nowNonow, string. Optional.
leafIndexNoleafIndex, integer, from 0 to 19. Optional.
certificatesYescertificates, array. Required.

Output Schema

NameRequiredDescriptionDefault
chainNochain. Array.
issuesNoissues. Array.
sourcesNosources. Array.
trustedNotrusted. Boolean.
rootStoreNorootStore. Object.
evaluatedAtNoevaluatedAt. String.
limitationsNolimitations. Array.
revocationCheckedNorevocationChecked. Boolean.

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?

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, and the description adds genuinely new operational facts: a $0.04 USDC price, the x402 payment flow, and that an unpaid call returns payment terms without executing. It stops short of describing what a successful response contains, but an output schema exists to cover that.

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?

Four short sentences, purpose front-loaded, then the cost and payment mechanics that an agent needs before calling. No redundancy or filler.

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 low-complexity, three-parameter tool with full schema coverage and an output schema, the description covers purpose, cost, and failure mode adequately. Only the sibling-differentiation and expected-result framing are absent, and the latter is supplied by the output schema.

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 schema fully documents certificates, leafIndex (0-19), and now. The description adds no syntax, ordering, or format detail beyond structured data, which is the expected baseline of 3.

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?

"Chain certificates against the vendored Mozilla root store" gives a specific verb (chain) and resource (certificates) plus the trust anchor used, which is more informative than a bare title restatement. It does not explicitly differentiate itself from siblings like x509-decode or tls-fingerprint-compute, so an agent must infer the boundary.

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: the agent can infer this is the tool for validating a certificate chain to Mozilla roots, and the payment note clarifies what happens on an unpaid call. There is no explicit when-to-use vs. when-not, and no routing to the adjacent x509-decode or csr-decode-validate 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