Skip to main content
Glama
jmaciasc-google

Google Threat Intelligence MCP Server

by jmaciasc-google
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_entities_related_to_a_domain

Retrieve related entities for a given domain, such as associated malware families, campaigns, subdomains, or DNS records, to investigate threats.

Instructions

Retrieve entities related to the the given domain.

The following table shows a summary of available relationships for domain objects.

Relationship

Description

Return type

associations

Domain's associated objects (reports, campaigns, IoC collections, malware families, software toolkits, vulnerabilities, threat-actors), without filtering by the associated object type.

Everyone.

caa_records

Records CAA for the domain.

domain

campaigns

Campaigns associated to the domain.

collection

cname_records

Records CNAME for the domain.

domain

collections

IoC Collections associated to the domain.

collection

comments

Community posted comments about the domain.

comment

communicating_files

Files that communicate with the domain.

file

downloaded_files

Files downloaded from that domain.

file

graphs

Graphs including the domain.

graph

historical_ssl_certificates

SSL certificates associated with the domain.

ssl-cert

historical_whois

WHOIS information for the domain.

whois

immediate_parent

Domain's immediate parent.

domain

malware_families

Malware families associated to the domain.

collection

memory_pattern_parents

Files having a domain as string on memory during sandbox execution.

file

mx_records

Records MX for the domain.

domain

ns_records

Records NS for the domain.

domain

parent

Domain's top parent.

domain

referrer_files

Files containing the domain.

file

related_comments

Community posted comments in the domain's related objects.

comment

related_reports

Reports that are directly and indirectly related to the domain.

collection

related_threat_actors

Threat actors related to the domain.

collection

reports

Reports directly associated to the domain.

collection

resolutions

DNS resolutions for the domain.

resolution

siblings

Domain's sibling domains.

domain

soa_records

Records SOA for the domain.

domain

software_toolkits

Software and Toolkits associated to the domain.

collection

subdomains

Domain's subdomains.

domain

urls

URLs having this domain.

url

user_votes

Current user's votes.

vote

votes

Domain's votes.

vote

vulnerabilities

Vulnerabilities associated to the domain.

collection

Args: domain (required): Domain to analyse. relationship_name (required): Relationship name. descriptors_only (required): Bool. Must be True when the target object type is one of file, domain, url, ip_address or collection. limit: Limit the number of entities to retrieve. 10 by default. Returns: List of entities related to the domain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
domainYes
descriptors_onlyYes
relationship_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4/5.0
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 adds value by listing available relationships and return types, and notes the required descriptors_only constraint. However, it does not disclose potential side effects, pagination behavior, or rate limits.

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 long due to the necessary relationship table. It is front-loaded with the purpose, but the table is somewhat repetitive. While informative, it could be more concise without losing essential detail.

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 an output schema exists, the description does not need to detail return values. It adequately covers parameter semantics, usage constraint, and relationship options. Lacks mention of pagination or maximum limit, but is generally complete for a complex tool.

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 coverage is 0%, so the description must compensate. It explains domain and relationship_name through the extensive table, clarifies descriptors_only with a usage constraint, and notes limit defaults to 10. This adds significant meaning beyond the bare schema.

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 starts with a clear verb+resource statement 'Retrieve entities related to the given domain.' and distinguishes from siblings like get_entities_related_to_a_file by focusing on domain objects.

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 guidance on when descriptors_only must be True ('Must be True when the target object type is one of file, domain, url, ip_address or collection') and specifies a default limit. However, it does not explicitly contrast with alternative tools or state when to choose this over similar sibling tools.

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/jmaciasc-google/gti-mcp-server'

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