Skip to main content
Glama
googleSandy

Google Threat Intelligence MCP Server

by googleSandy

get_collection_timeline_events

Retrieve curated timeline events from threat intelligence collections for campaigns and threat actors, grouped by event category.

Instructions

Retrieves timeline events from the given collection, when available.

This is super valuable curated information produced by security analysits at Google Threat Intelligence.

We should fetch this information for campaigns and threat actors always.

It's common to display the events grouped by the "event_category" field.

Args: id (required): Collection identifier Return: List of events related to the given collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
api_keyNo

Implementation Reference

  • Handler function that retrieves timeline events for a collection by calling the /collections/{id}/timeline/events API endpoint. Returns a sanitized list of events on success, or an error dict on non-200 response.
    @server.tool()
    async def get_collection_timeline_events(id: str, ctx: Context, api_key: str = None):
      """Retrieves timeline events from the given collection, when available.
    
      This is super valuable curated information produced by security analysits at Google Threat Intelligence.
    
      We should fetch this information for campaigns and threat actors always.
    
      It's common to display the events grouped by the "event_category" field.
    
      Args:
        id (required): Collection identifier
      Return:
        List of events related to the given collection.
      """
      async with vt_client(ctx, api_key=api_key) as client:
        resp = await client.get_async(f"/collections/{id}/timeline/events")
        if resp.status != 200:
            error_json = await resp.json_async()
            error_info = error_json.get("error", {})
            return [{"error": f"API Error: {error_info.get('message', 'Unknown error')}"}]
        data = await resp.json_async()
      return utils.sanitize_response(data.get("data", []))
  • Tool is registered via the @server.tool() decorator, which binds it to the FastMCP server instance from gti_mcp/server.py. The tools module is imported via 'from gti_mcp.tools import *' in server.py:73
    @server.tool()
  • Helper utility used to remove empty dicts/lists from the response data before returning to the caller.
    def sanitize_response(data: typing.Any) -> typing.Any:
      """Removes empty dictionaries and lists recursively from a response."""
      if isinstance(data, dict):
        sanitized_dict = {}
        for key, value in data.items():
          sanitized_value = sanitize_response(value)
          if sanitized_value is not None:
            sanitized_dict[key] = sanitized_value
        return sanitized_dict
      elif isinstance(data, list):
        sanitized_list = []
        for item in data:
          sanitized_item = sanitize_response(item)
          if sanitized_item is not None:
            sanitized_list.append(sanitized_item)
        return sanitized_list
      elif isinstance(data, str):
        return data if data else None
      else:
        return data
  • The server imports all tools (including collections.py) from gti_mcp.tools, which registers all @server.tool() decorated functions.
    # Load tools.
    from gti_mcp.tools import *
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states events are retrieved 'when available', implying possible empty results, but does not disclose auth requirements (api_key parameter not described), rate limits, error handling, or side effects. The read-only nature is implied but not confirmed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph with separate Args/Return section, which is decently structured. However, it includes redundant phrasing ('super valuable', 'always') and could be more concise. The key information is front-loaded in the first sentence.

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

Completeness3/5

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

The tool has 2 parameters (1 required), no output schema, and moderate complexity. The description covers purpose and usage guidance but omits parameter details for api_key, does not describe event structure beyond 'list', and lacks error or empty result handling. It is sufficient for basic use but not comprehensive.

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

Parameters2/5

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

The description adds meaning for the 'id' parameter (collection identifier) and return type (list of events). However, it completely ignores the 'api_key' parameter, which is part of the input schema with a default of null. With 0% schema description coverage, the description should cover all parameters; it fails to explain the api_key role.

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?

The description clearly states it retrieves timeline events from a collection, with a specific verb and resource. It adds context about the value ('curated information by security analysts') and suggests use for campaigns and threat actors. While it doesn't explicitly differentiate from sibling collection tools, the resource is uniquely identified.

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 explicitly advises using this tool for campaigns and threat actors ('always'), and notes common display grouping by event_category. It does not mention when not to use or alternatives, but the provided guidance is direct and actionable.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/googleSandy/gti-mcp-standalone'

If you have feedback or need assistance with the MCP directory API, please join our Discord server