Skip to main content
Glama
jmaciasc-google

Google Threat Intelligence MCP Server

get_entities_related_to_an_ip_address

Query relationships of an IP address to find associated campaigns, files, malware families, and other threat intelligence data.

Instructions

Retrieve entities related to the the given IP Address.

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

Relationship

Description

Return type

associations

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

collection

campaigns

Campaigns associated to the IP address.

collection

collections

IoC Collections associated to the IP address.

collection

comments

Comments for the IP address.

comment

communicating_files

Files that communicate with the IP address.

file

downloaded_files

Files downloaded from the IP address.

file

graphs

Graphs including the IP address.

graph

historical_ssl_certificates

SSL certificates associated with the IP.

ssl-cert

historical_whois

WHOIS information for the IP address.

whois

malware_families

Malware families associated to the IP address.

collection

memory_pattern_parents

Files having an IP as string on memory during sandbox execution.

file

referrer_files

Files containing the IP address.

file

related_comments

Community posted comments in the IP's related objects.

comment

related_reports

Reports that are directly and indirectly related to the IP.

collection

related_threat_actors

Threat actors related to the IP address.

collection

reports

Reports directly associated to the IP.

collection

resolutions

IP address' resolutions

resolution

software_toolkits

Software and Toolkits associated to the IP address.

collection

urls

URLs related to the IP address.

url

user_votes

IP's votes made by current signed-in user.

vote

votes

IP's votes.

vote

vulnerabilities

Vulnerabilities associated to the IP address.

collection

Args: ip_address (required): IP Addres 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 IP Address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
ip_addressYes
descriptors_onlyYes
relationship_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations exist, so the description must fully disclose behavior. It mentions that descriptors_only must be True for certain object types, and describes the return type per relationship via the table. However, it does not cover pagination, error handling, or permission requirements.

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 front-loaded with a clear purpose sentence. The table adds length but is well-structured and necessary for parameter clarity. It is verbose but not wasteful.

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

Completeness5/5

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

Given the output schema exists and the description covers all parameters with a detailed relationship table, it is complete for the tool's complexity. It provides sufficient context for an AI agent to understand the tool's capabilities.

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 adds crucial meaning. It explains ip_address, relationship_name (with a table of valid values), descriptors_only (boolean constraint), and limit (default 10). The table effectively enriches the relationship_name parameter beyond the 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 clearly states it retrieves entities related to an IP address, and the detailed table of relationships with descriptions and return types makes the purpose very specific. It distinguishes itself from sibling tools like get_entities_related_to_a_domain by focusing on IP addresses.

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 does not provide any guidance on when to use this tool versus alternatives (e.g., other get_entities_related_to_* tools). There are no explicit conditions, exclusions, or prerequisites mentioned.

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