Skip to main content
Glama
googleSandy

Google Threat Intelligence MCP Server

by googleSandy

search_software_toolkits

Search for software toolkits in Google's Threat Intelligence platform to identify threats and malware collections for security analysis.

Instructions

Search software toolkits (or just tools) in the Google Threat Intelligence platform.

Software toolkits are modeled as collections. Once you get collections from this tool, you can use get_collection_report to fetch the full reports and their relationships.

You can use order_by to sort the results by: "relevance", "creation_date". You can use the sign "+" to make it order ascending, or "-" to make it descending. By default is "relevance-"

Args: query (required): Search query to find threats. limit: Limit the number of threats to retrieve. 10 by default. order_by: Order results by the given order key. "relevance-" by default.

Returns: List of collections, aka threats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
limitNo
order_byNorelevance-
api_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function search_software_toolkits decorated with @server.tool() for registration. It accepts query, ctx, limit, order_by, and api_key parameters, and delegates to _search_threats_by_collection_type with collection_type hardcoded as 'software-toolkit'
    @server.tool()
    async def search_software_toolkits(
        query: str, ctx: Context, limit: int = 10, order_by: str = "relevance-", api_key: str = None
    ) -> typing.List[typing.Dict[str, typing.Any]]:
      """Search software toolkits (or just tools) in the Google Threat Intelligence platform.
    
      Software toolkits are modeled as collections. Once you get collections from this tool, you can use `get_collection_report` to fetch the full reports and their relationships.
    
      You can use order_by to sort the results by: "relevance", "creation_date". You can use the sign "+" to make it order ascending, or "-" to make it descending. By default is "relevance-"
    
      Args:
        query (required): Search query to find threats.
        limit: Limit the number of threats to retrieve. 10 by default.
        order_by: Order results by the given order key. "relevance-" by default.
    
      Returns:
        List of collections, aka threats.
      """
      res = await _search_threats_by_collection_type(
          query, "software-toolkit", ctx, limit, order_by, api_key=api_key)
      return res
  • Helper function _search_threats_by_collection_type that handles the core logic for searching threats by collection type. It validates the collection_type, makes API calls via vt_client, and returns sanitized results using utils.sanitize_response
    async def _search_threats_by_collection_type(
        query: str,
        collection_type: str,
        ctx: Context,
        limit: int = 10,
        order_by: str = "relevance-",
        api_key: str = None,
    ) -> typing.List[typing.Dict[str, typing.Any]]:
      """Search a given threat type in the Google Threat Intelligence platform,
    
      Args:
        query (required): Search query to find threats. If you want any threat, just pass an empty string.
        collection_type (required): Collection type. One of: "threat-actor", "malware-family", "campaign", "report", "vulnerability", "collection".
        limit: Limit the number of threats to retrieve. 10 by default.
        order_by: Order results by the given order key. "relevance-" by default.
    
      Returns:
        List of collections, aka threats.
      """
      if collection_type not in COLLECTION_TYPES:
          raise ValueError(
              f"wrong collection_type. Available collection_type are: {','.join(COLLECTION_TYPES)} ")
    
      async with vt_client(ctx, api_key=api_key) as client:
        res = await utils.consume_vt_iterator(
            client,
            "/collections",
            params={
                "filter": f"collection_type:{collection_type} {query}",
                "order": order_by,
                "relationships": COLLECTION_KEY_RELATIONSHIPS,
                "exclude_attributes": COLLECTION_EXCLUDED_ATTRS,
            },
            limit=limit,
        )
      return utils.sanitize_response([o.to_dict() for o in res])
  • Collection type schema definition (COLLECTION_TYPES set) that defines valid collection types including 'software-toolkit' which is used by search_software_toolkits
    COLLECTION_TYPES = {
        "threat-actor",
        "malware-family",
        "campaign",
        "report",
        "software-toolkit",
        "vulnerability",
        "collection",
    }
  • Tool registration via @server.tool() decorator on the search_software_toolkits function
    @server.tool()
Behavior3/5

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

With no annotations provided, the description carries the full burden. It explains the return type ('List of collections, aka threats') and mentions default values for 'limit' and 'order_by', which is helpful. However, it doesn't disclose important behavioral traits like authentication requirements (implied by 'api_key' parameter but not stated), rate limits, error conditions, or pagination behavior for large result sets.

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 well-structured and front-loaded: it starts with the core purpose, then provides usage context, parameter details, and return value. Every sentence adds value without redundancy. The bullet-point style for parameters is clear and efficient.

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?

Given the tool has an output schema (returns 'List of collections'), the description doesn't need to detail return values. It covers the purpose, basic usage flow, and parameter semantics reasonably well. However, for a search tool with authentication requirements (implied by 'api_key'), the description could better address behavioral aspects like error handling or result limitations.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It provides meaningful explanations for all three main parameters: 'query' is for 'search query to find threats', 'limit' controls 'number of threats to retrieve', and 'order_by' includes syntax details (+/- for ascending/descending) and valid values ('relevance', 'creation_date'). The 'api_key' parameter is not mentioned in the description, leaving a gap.

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 the tool searches for 'software toolkits (or just tools) in the Google Threat Intelligence platform' and specifies they are 'modeled as collections'. It distinguishes from siblings by focusing on software toolkits specifically, though it doesn't explicitly contrast with similar search tools like 'search_threats' or 'search_malware_families'.

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 provides clear context by explaining that results from this tool can be used with 'get_collection_report' to fetch full reports, establishing a workflow. However, it doesn't explicitly state when to use this versus other search tools (e.g., 'search_threats' or 'search_malware_families'), which are listed as siblings.

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