Skip to main content
Glama

BRAINIAC Network Exposure & Certificate Tooling

Fingerprint and audit SSH public keys

network-exposure_ssh-key-audit
Read-onlyIdempotent

Parse OpenSSH public keys, authorized_keys and certificates. Price $0.02 USDC. POST /api/v1/network-exposure/ssh-key-audit. 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": {
      "keys": "<keys>"
    },
    "name": "network-exposure_ssh-key-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYeskeys, array. Required.
minRsaBitsNominRsaBits, integer, from -9007199254740991 to 9007199254740991. Required.

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
limitationsNolimitations. 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 declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the $0.02 USDC price and the fact that an unpaid call returns x402 payment terms without executing. That payment-gating detail is exactly the kind of context annotations cannot express. It stops short of a 5 because it says nothing about output shape, rate limits, or whether submitted keys are retained.

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?

Three short sentences, front-loaded with the capability before the commercial and transport details. Every sentence carries information, though the raw POST path is marginal value for an agent that only needs the tool name. No filler or repetition.

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 no explanation, and the payment flow is covered. However, for a security audit tool the description never indicates what the audit actually evaluates (weak key sizes, weak algorithms, certificate validity), leaving the agent to infer the findings model. Adequate but with a clear gap for a two-parameter, payment-gated service.

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 both parameters are already documented structurally, and the description adds nothing about the keys array format or the minRsaBits threshold. Baseline 3 applies when the schema does the work. No syntax or format hints (e.g., expected key prefixes) are supplied to compensate.

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 first sentence names a specific verb and resource set: parse OpenSSH public keys, authorized_keys files, and certificates. That is enough to distinguish it from siblings like x509-decode or csr-decode-validate, which handle different input formats. It does not explicitly say how it differs from those adjacent parsers, which keeps it 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to reach for this tool versus the X.509 or CSR siblings, and no prerequisites or input expectations are stated. The only conditional behavior described is payment-related, not usage-related. The agent must infer the use case entirely from the verb and resource.

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