Skip to main content
Glama

BRAINIAC Threat Intelligence & Public Signals

Aggregate public threat feeds

threat-intelligence_public-threat-feed-aggregate
Read-onlyIdempotent

Aggregate caller-supplied and verified key-free public threat feeds (CISA KEV, OpenPhish, capped PhishTank). URLhaus/ThreatFox require auth and are not queried. Feed hits are not confirmed malice. Price $0.05 USDC. POST /api/v1/threat-intelligence/public-threat-feed-aggregate. 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_public-threat-feed-aggregate"
  }
}

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.
feedCountNofeedCount. Number.
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.8/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: a $0.05 USDC price, the x402 payment-gate behavior (an unpaid call returns payment terms and does not run), which feeds are unavailable due to auth, and an interpretive caveat that feed hits are not confirmed malice. The annotations already cover read-only/idempotent/open-world traits, and this content complements them well; only the shape of the aggregate result is left to the output schema.

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?

Five terse sentences, front-loaded with sources and exclusions before the commercial terms. Every sentence carries decision-relevant information: scope, auth exclusions, interpretive caveat, price, endpoint, and payment failure mode.

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 read-only aggregation tool with a full output schema and annotated safety profile, the description covers the commercially critical unknowns (cost, payment gating) and the trust caveat. The remaining gap is how the many caller-supplied input collections relate to the feed fetch, which is non-obvious given 21 loosely described parameters.

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 every parameter is technically documented, which sets the baseline at 3. That said, the schema descriptions are pure boilerplate ('csv, string, length 0 to 200000'), and the description does not clarify the opaque caller-supplied payload families (feeds, indicators, brands, domains, services, certificates) or the fetch* toggles, so no extra meaning is added.

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 (aggregate public threat feeds) and enumerates the actual sources queried (CISA KEV, OpenPhish, capped PhishTank), which pins down scope precisely. It does not name a sibling tool, so differentiation is achieved indirectly through the 'key-free public feeds' framing rather than explicit routing.

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 description gives a useful exclusion rule ('URLhaus/ThreatFox require auth and are not queried'), which tells the agent what this tool will not cover. However, it never states when an agent should choose this aggregate over siblings like ioc-context-enrich or threat-indicator-confidence-score, leaving selection to inference from the tool name.

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