Skip to main content
Glama

BRAINIAC Network Exposure & Certificate Tooling

Fingerprint service banners with Recog

network-exposure_service-banner-fingerprint
Read-onlyIdempotent

Match banners against vendored Rapid7 Recog fingerprints. Price $0.03 USDC. POST /api/v1/network-exposure/service-banner-fingerprint. 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": {
      "items": "<items>"
    },
    "name": "network-exposure_service-banner-fingerprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesitems, array. Required.

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
recogRevisionNorecogRevision. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds genuinely non-obvious behavior: the $0.03 USDC price, the x402 payment-required response, and the fact that an unpaid call does not execute the fingerprint match. It stops short of describing match confidence or what a miss returns.

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?

Three short sentences, front-loaded with the operation, followed by price, endpoint, and the unpaid-call caveat. No filler and nothing buried.

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?

An output schema exists, so return values need not be explained, and the payment/execution semantics are covered. The remaining gap is the content of the items array, but overall the definition is sufficient to invoke the tool correctly.

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 a baseline of 3 applies. However, the schema's own descriptions are generic placeholders ("type, string, length 1 to 64"), and the tool description never clarifies what a banner item's type or value should contain for Recog matching, which is the one piece of meaning an agent actually needs.

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: "Match banners against vendored Rapid7 Recog fingerprints." That is distinctive against siblings such as tls-fingerprint-compute or x509-decode, though it never explicitly contrasts itself with them.

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 statement of when to choose this tool over the TLS, CPE, or Nmap siblings, nor any prerequisite or input-shape guidance. The only usage condition given is the payment state (unpaid calls return x402 terms), which is billing, not tool selection.

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