Skip to main content
Glama

check_realtime_threat_feed

Read-onlyIdempotent

Checks a domain against a real-time threat intelligence feed to detect active threats, separate from DNSBL checks, and returns informational status when the feed is unprovisioned.

Instructions

Check a domain against BlackVeil real-time threat intelligence (curated intel-gateway feed). Distinct from DNSBL checks. Operator-deploy only; degrades to info when unprovisioned.

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": {
      "domain": "<domain>"
    },
    "name": "check_realtime_threat_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain, e.g. example.com
formatNoOutput verbosity.
force_refreshNoBypass the cache.

Output Schema

NameRequiredDescriptionDefault
scoreYes
passedYes
partialNo
categoryYes
findingsYes
checkStatusNo
verdictWithheldNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.111.2
    • changedInput schema / properties / domain / description
      Previous value: -"Domain to check (e.g., example.com)"New value: +"Domain, e.g. example.com"
    • changedInput schema / properties / force_refresh / description
      Previous value: -"Bypass cache and run a fresh check. Useful after DNS changes."New value: +"Bypass the cache."
    • changedInput schema / properties / format / description
      Previous value: -"Output verbosity. Auto-detected if omitted."New value: +"Output verbosity."
  2. Changed1 schema field changedv3.103.1
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed1 schema field changedv3.98.1
    • addedOutput schema / properties / verdictWithheld
      Added value: +{
      +  "type": "boolean"
      +}
  4. Changed2 schema fields changedv3.54.0
    • addedOutput schema / properties / checkStatus
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / partial
      Added value: +{
      +  "type": "boolean"
      +}
  5. Addedv3.37.0
  6. Removedv3.31.1
  7. First observedv3.29.7

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world semantics, so the description earns credit for what it adds: provisioning dependency and graceful degradation to informational output when unprovisioned. That degradation note is genuinely useful operational context absent from annotations. It doesn't mention rate limits or result freshness beyond the curated-feed framing.

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 compact sentences with no filler; purpose first, differentiation second, operational caveat last. Every clause carries information an agent would otherwise have to guess.

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?

With an output schema present, return-value detail is not required, and the description supplies the deployment caveat an agent needs to interpret empty/info responses. The only omission is what a positive or degraded result implies for follow-up action, which is minor for a single-domain lookup.

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%, including the format enum and force_refresh cache-bypass meaning, so the schema already carries parameter semantics. The description mentions the cache only obliquely via 'real-time' and adds no format or domain-syntax guidance. Baseline 3 applies when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb (check) plus object (domain) against a named intelligence source (BlackVeil real-time threat intelligence, curated intel-gateway feed), and explicitly separates itself from DNSBL checks. An agent can distinguish it from check_rbl/check_dbl without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The sentence 'Distinct from DNSBL checks' gives a clear selection rule against the blocklist siblings, and 'Operator-deploy only' signals a deployment prerequisite. It stops short of an explicit when-to-use scenario (e.g. 'use for newly observed domains not yet in blocklists'), so guidance is clear but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools