Skip to main content
Glama

Nullcone Threat Intelligence

by io.github.maco144

drain_subscription

Drain the buffer of a stateful subscription created by subscribe_threats().

Returns all IOCs delivered to this subscription since the last drain.
Each subscription is independent — draining yours does not affect others.

Args:
    subscription_id: The ID returned by subscribe_threats()
    drain:           If True (default), clear the buffer after returning.
                     Set False to peek without consuming.

Returns:
    signatures:      List of new threat signatures
    count:           Number of signatures returned
    buffered:        Total signatures currently in buffer
    push_active:     Whether the background push subscription is running

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
drainNo
subscription_idYes

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it explains the mutating drain behavior, the default clearing, the peek option, and the independence of subscriptions. It also documents all return fields, including whether the background push is active, which is useful runtime information.

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?

The description is tight and well-structured, opening with a one-sentence summary followed by clear Args and Returns sections. Every sentence earns its place, with no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given there is no output schema, the Returns section is essential and well-accounted for. The tool's behavior, parameters, side effects, independence property, and response surface are all covered, making it fully usable for a consumer of a stateful subscription API.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description fully compensates by explaining both parameters: subscription_id is the output of subscribe_threats(), and drain defaults to true with an explicit peek use-case. This adds meaningful semantics beyond the bare schema names and types.

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?

The description uses a specific verb ('drain') and resource ('buffer of a stateful subscription'), and explicitly links it to subscribe_threats(). It distinguishes itself from sibling tools by explaining it returns IOCs delivered since the last drain and that subscriptions are independent.

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 description clearly states this tool is for draining a buffer created by subscribe_threats(), giving concrete context for when to use it. It does not explicitly name exclusionary alternatives like get_new_threats, but the stateful subscription context is enough to guide selection.

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

All Nullcone Threat Intelligence toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but there is notable overlap among threat-fetching methods: get_new_threats, poll_since, and drain_subscription all retrieve new threats via different mechanisms, and several stats tools (get_stats, freshness_limits, prompt_cache_stats) serve similar informational roles. Overall, descriptions help disambiguate, but a few tools could be confused.

Naming Consistency3/5

The naming is predominantly snake_case, but mixes verb_noun (check_freshness, submit_ioc), noun phrases (family_threats, freshness_limits), and even a question (is_ioc_revoked). 'unsubscribe' breaks the pattern of other subscription tools (subscribe_threats, drain_subscription). This inconsistency is noticeable though still readable.

Tool Count3/5

30 tools is on the heavy side for a single MCP server, exceeding the typical 15-tool comfort zone. However, the server covers a broad domain—IOC submission, retrieval, subscriptions, freshness tracking, prompt/skill scanning, and registry monitoring—so the large number is somewhat justified by the scope.

Completeness4/5

The tool surface covers the full threat intelligence lifecycle: submit (submit_ioc, submit_batch), query (lookup_ioc, search_by_type, recent_threats, family_threats), subscribe (subscribe_threats, drain_subscription), update (report_detection, vote_false_positive), and revoke (revoke_ioc). Minor gaps exist, such as the absence of a direct delete or update signature tool and no get-by-signature-id endpoint, but these are manageable for agents.

Resources