Skip to main content
Glama

BRAINIAC Threat Intelligence & Public Signals

Analyze exposed service risk

threat-intelligence_exposed-service-risk-analyze
Read-onlyIdempotent

Analyze caller-supplied external service inventory and scan results for exposure risk. Never initiates intrusive network scanning. Price $0.04 USDC. POST /api/v1/threat-intelligence/exposed-service-risk-analyze. 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_exposed-service-risk-analyze"
  }
}

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 declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: it never initiates intrusive scanning, it costs $0.04 USDC, and an unpaid call returns x402 payment terms without executing — details no annotation or schema conveys. It doesn't describe rate limits or what the risk output contains, but the output schema covers returns.

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 short sentences, front-loaded with purpose, followed by the safety constraint, price, endpoint and payment failure behavior. The POST path is arguably noise for an agent, but the pricing and non-execution rule earn their place.

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 complex 21-parameter tool with nested objects and an output schema, the description covers the decisive unknowns: no active scanning, paid invocation model, and unpaid-call behavior. What remains (which optional enrichment inputs to supply) is left to the fully documented 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% across 21 parameters, so the schema already documents every field. The phrase 'external service inventory and scan results' loosely hints at the services/domains/csv inputs, but it adds no meaning about the many fetch* toggles, staleDays, or feed/indicator inputs beyond what the schema states.

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 ('Analyze caller-supplied external service inventory and scan results for exposure risk') and explicitly scopes the input as caller-supplied rather than actively collected, which separates it from active-scanning expectations. It doesn't name or contrast any sibling tool, so the differentiation is only implicit.

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 implied by 'caller-supplied ... inventory and scan results' — you use it when you already hold exposure data — but there is no explicit when-to-use, when-not, or pointer to an alternative among the sibling threat-intelligence 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