Skip to main content
Glama

Nullcone Threat Intelligence

by io.github.maco144

list_revocations

List recent IOC revocations, newest first.

Args:
    limit:       Maximum number of revocations to return (default 50).
    since_hours: Only return revocations newer than this many hours ago.
                 0 = no time filter (return all retained).

Returns:
    revocations: List of revocation event dicts.
    total:       Total revocations in the registry.
    stats:       Counts by reason.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
since_hoursNo

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the transparency burden. It discloses ordering ('newest first'), filtering behavior ('since_hours' with 0 meaning no time filter), and return semantics ('all retained'). It does not detail pagination or retention limitations, but for a list tool this is reasonably transparent.

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 compact and well-structured: a one-sentence purpose, then Args and Returns sections. Every line contributes meaning, and the front-loaded verb phrase makes the tool's purpose immediately clear. No filler or redundancy.

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 the tool's simplicity, two optional parameters, and no output schema, the description is complete. It documents each parameter's behavior and all three return components ('revocations', 'total', 'stats'), so an agent can invoke and interpret results without additional context.

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 description coverage is 0%, so the description fully compensates by explaining both parameters: 'limit' is the maximum number to return (default 50), and 'since_hours' filters to revocations newer than N hours with 0 meaning no time filter. This goes well beyond the schema's bare type/default declarations.

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 opens with 'List recent IOC revocations, newest first,' which is a specific verb+resource statement that clearly identifies the tool's function and output ordering. This distinguishes it from sibling tools like revoke_ioc (which performs a write) and is_ioc_revoked (which checks a single IOC).

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 gives clear context for when to use the tool—when you need recent revocation events—and explains the two filtering parameters with their defaults. It does not explicitly mention exclusions or alternatives, but the list vs. check vs. revoke distinction is apparent from the wording.

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