Skip to main content
Glama

BRAINIAC Threat Intelligence & Public Signals

Cluster certificate relationships

threat-intelligence_certificate-threat-cluster
Read-onlyIdempotent

Identify relationships between domains using caller-supplied certificates and optional public crt.sh data. Shared certificate attributes are linkage evidence, not confirmed abuse. Price $0.04 USDC. POST /api/v1/threat-intelligence/certificate-threat-cluster. 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": "threat-intelligence_certificate-threat-cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNocsv, string, length 0 to 200000. Optional.
asOfNoasOf, string, length 0 to 40. Optional.
fileNofile, object. Optional.
jsonNojson, string, length 0 to 200000. Optional.
textNotext, string, length 0 to 200000. Optional.
feedsNofeeds, array. Optional.
filesNofiles, array. Optional.
brandsNobrands, array. Optional.
domainsNodomains, array. Optional.
servicesNoservices, array. Optional.
fetchRdapNofetchRdap, boolean. Optional.
publicDnsNopublicDns, boolean. Optional.
staleDaysNostaleDays, number, from 1 to 365. Optional.
candidatesNocandidates, array. Optional.
crtShQueryNocrtShQuery, string, length 0 to 253. Optional.
fetchCrtShNofetchCrtSh, boolean. Optional.
indicatorsNoindicators, array. Optional.
certificatesNocertificates, array. Optional.
fetchCisaKevNofetchCisaKev, boolean. Optional.
fetchOpenPhishNofetchOpenPhish, boolean. Optional.
fetchPhishTankNofetchPhishTank, boolean. Optional.

Output Schema

NameRequiredDescriptionDefault
itemsNoitems. Array.
statusNostatus. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
itemCountNoitemCount. Number.
limitationsNolimitations. Array.
apiKeyRequiredNoapiKeyRequired. Boolean.
sourceStatusesNosourceStatuses. Array.
paidProviderUsedNopaidProviderUsed. Boolean.
publicDnsQueriedNopublicDnsQueried. Boolean.
publicFetchesUsedNopublicFetchesUsed. Boolean.
intrusiveScanPerformedNointrusiveScanPerformed. Boolean.
singleWeakSignalMaliciousClaimedNosingleWeakSignalMaliciousClaimed. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, open-world, idempotent, non-destructive), and the description adds genuinely new operational facts: a $0.04 USDC price, an HTTP POST endpoint, and the x402 gating behavior where an unpaid call returns payment terms and does not execute. It also sets expectations about evidentiary strength of the output.

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 compact sentences, purpose front-loaded, followed by interpretive caveat, price, endpoint, and payment behavior. Every sentence carries information, though the raw endpoint path is arguably the least valuable element for an agent deciding whether to call.

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?

Given an output schema exists and annotations declare the safety and open-world profile, the description covers the remaining unknowns an agent needs: cost, payment gating, and the epistemic status of the results. It stops short of describing rate limits or whether a paid call can partially fail, but nothing essential to deciding or invoking is missing.

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 21 parameters and their nested shapes are already documented structurally. The description only loosely signals which inputs matter (certificates array, crt.sh options) without explaining fields like asOf, staleDays, candidates, or the many fetcher booleans. Baseline 3 applies when the schema carries the load.

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?

States a specific verb and resource: identify relationships between domains using caller-supplied certificates, plus optional crt.sh enrichment. An agent can tell this is certificate-based clustering rather than, say, typosquatting detection, though it never names a sibling to contrast against.

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?

Implies the input mode (caller-supplied certificates, optional public crt.sh) and warns that shared certificate attributes are linkage evidence rather than confirmed abuse, which shapes how results should be used. There is no explicit when-to-use or when-not-to-use guidance versus the other clustering tools in the catalog.

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