Skip to main content
Glama
googleSandy

Google Threat Intelligence MCP Server

by googleSandy

get_url_report

Analyze URLs for security threats using Google Threat Intelligence to identify malicious content and assess reputation.

Instructions

Get a comprehensive URL analysis report from Google Threat Intelligence.

Args: url (required): URL to analyse. Returns: Report with insights about the URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
api_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Main handler function for the get_url_report tool. It converts the URL to base64, fetches the report from Google Threat Intelligence API with associations, and returns a sanitized response.
    @server.tool()
    async def get_url_report(url: str, ctx: Context, api_key: str = None) -> typing.Dict[str, typing.Any]:
      """Get a comprehensive URL analysis report from Google Threat Intelligence.
    
      Args:
        url (required): URL to analyse.
      Returns:
        Report with insights about the URL.
      """
      url_id = url_to_base64(url)
      async with vt_client(ctx, api_key=api_key) as client:
        res = await utils.fetch_object(
            client,
            "urls",
            "url",
            url_id,
            relationships=["associations"],
            params={"exclude_attributes": "last_analysis_results"})
      return utils.sanitize_response(res)
  • Helper function that converts a URL string to base64 encoding without padding, as required by the Google Threat Intelligence API for URL identifiers.
    def url_to_base64(url: str) -> str:
      """Converts the URL into base64.
    
      Without padding, as required by the Google Threat Intelligence API.
      """
      b = base64.b64encode(url.encode('utf-8'))
      return b.decode('utf-8').rstrip("=")
  • Helper function that fetches objects from the Google Threat Intelligence API with support for filtering by attributes and relationships, and handles API errors gracefully.
    async def fetch_object(
        vt_client: vt.Client,
        resource_collection_type: str,
        resource_type: str,
        resource_id: str,
        attributes: list[str] | None = None,
        relationships: list[str] | None = None,
        params: dict[str, typing.Any] | None = None):
      """Fetches objects from Google Threat Intelligence API."""
      logging.info(
          f"Fetching comprehensive {resource_collection_type} "
          f"report for id: {resource_id}")
      
      params = {k: v for k, v in params.items()} if params else {}
    
      # Retrieve a selection of object attributes and/or relationships.
      if attributes:
        params["attributes"] = ",".join(attributes)
      if relationships:
        params["relationships"] = ",".join(relationships)
    
      try:
        obj = await vt_client.get_object_async(
            f"/{resource_collection_type}/{resource_id}", params=params)
    
        if obj.error:
          logging.error(
              f"Error fetching main {resource_type} report for {resource_id}: {obj.error}"
          )
          return {
              "error": f"Failed to get main {resource_type} report: {obj.error}",
              # "details": report.get("details"),
          }
      except vt.error.APIError as e:
        logging.warning(
            f"VirusTotal API Error fetching {resource_type} {resource_id}: {e.code} - {e.message}"
        )
        return {
            "error": f"VirusTotal API Error: {e.code} - {e.message}",
            "details": f"The requested {resource_type} '{resource_id}' could not be found or there was an issue with the API request."
        }
      except Exception as e:
        logging.exception(
            f"Unexpected error fetching {resource_type} {resource_id}: {e}"
        )
        return {"error": "An unexpected internal error occurred."}
    
      # Build response.
      obj_dict = obj.to_dict()
      obj_dict['id'] = obj.id
      if 'aggregations' in obj_dict['attributes']:
        del obj_dict['attributes']['aggregations']
    
      logging.info(
          f"Successfully generated concise threat summary for id: {resource_id}")
      return obj_dict
  • Helper function that recursively removes empty dictionaries, lists, and empty strings from API responses to provide cleaner output to users.
    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
  • Registration point where all tools from gti_mcp.tools are imported. The get_url_report function is automatically registered as an MCP tool via the @server.tool() decorator in urls.py.
    # 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 the full burden of behavioral disclosure. It mentions 'comprehensive URL analysis report' but doesn't specify what that includes (e.g., threat indicators, reputation scores, historical data). It also doesn't disclose authentication needs (though 'api_key' is in the schema), rate limits, or whether this is a read-only operation. The description is too vague about behavioral traits.

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

Conciseness4/5

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

The description is appropriately sized and front-loaded, with the core purpose stated first. The 'Args' and 'Returns' sections are structured clearly. However, the 'Returns' section is redundant given the output schema exists, and some sentences could be more informative.

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?

Given the tool's moderate complexity (URL analysis), no annotations, and an output schema, the description is partially complete. It covers the basic purpose but lacks details on authentication, behavioral traits, and parameter semantics. The output schema reduces the need to explain return values, but the description should still address gaps like usage guidelines and transparency.

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?

Schema description coverage is 0%, so the description must compensate. It only mentions 'url (required): URL to analyse' and 'Returns: Report with insights about the URL.' It doesn't explain the 'api_key' parameter at all, nor does it provide format details for the URL (e.g., must be fully qualified). With 2 parameters and 0% schema coverage, this minimal information is insufficient.

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's purpose: 'Get a comprehensive URL analysis report from Google Threat Intelligence.' It specifies the verb ('Get'), resource ('URL analysis report'), and source ('Google Threat Intelligence'). However, it doesn't explicitly differentiate from sibling tools like 'get_domain_report' or 'get_ip_address_report', which perform similar analyses on different resource types.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_domain_report' or 'get_ip_address_report' for analyzing different resource types, nor does it specify prerequisites or exclusions. The only implied context is analyzing URLs, but no explicit usage guidelines are provided.

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