Skip to main content
Glama
googleSandy

Google Threat Intelligence MCP Server

by googleSandy

get_url_report

Analyze a URL to receive a comprehensive threat intelligence report covering reputation and security insights.

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

  • The main handler function for the 'get_url_report' tool. It base64-encodes the URL, fetches a comprehensive report from the Google Threat Intelligence API using the VirusTotal client (with 'associations' relationship), and sanitizes the 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 to its base64 representation (without padding) as required by the Google Threat Intelligence API.
    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("=")
  • Core utility function called by get_url_report. Fetches an object from the VirusTotal API, handling errors and sanitizing the response by removing 'aggregations' from attributes.
    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
  • Utility function that recursively removes empty dictionaries and lists from the API response before returning it.
    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.tool() decorator registers this function as an MCP tool named 'get_url_report' with the server.
    @server.tool()
    async def get_url_report(url: str, ctx: Context, api_key: str = None) -> typing.Dict[str, typing.Any]:
Behavior2/5

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

No annotations provided, so description carries full burden. It states a report is returned but discloses no behavioral traits like authentication needs (api_key param omitted), rate limits, or error behavior on invalid URLs.

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?

Description is very concise with three short sentences, front-loading the main purpose. However, it sacrifices necessary detail for brevity, missing key information about the api_key parameter.

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?

While an output schema exists (so return values need not be detailed), the description omits important context such as authentication via api_key, prerequisites for the URL, and typical use case for threat intelligence. Basic completeness but with gaps.

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% (no descriptions for parameters). Description only explains the 'url' parameter as required but ignores the 'api_key' parameter entirely, leaving its purpose and usage unclear.

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 clearly states the tool retrieves a comprehensive URL analysis report from Google Threat Intelligence, specifying the resource (URL) and action (get report). This distinguishes it from siblings like get_domain_report or get_file_report.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives such as get_domain_report or get_ip_address_report. The description does not mention prerequisites like API key or valid URL, nor does it specify context (e.g., for threat analysis).

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