Skip to main content
Glama
googleSandy

Google Threat Intelligence MCP Server

by googleSandy

create_collection

Create a new collection to group indicators of compromise such as domains, IPs, files, or URLs. Set description and privacy for organized threat intelligence analysis.

Instructions

Creates a new collection in Google Threat Intelligence. Ask for the collection's privacy (public or private) if the user doesn't specify.

Args: name (required): The name of the collection. description (required): A description of the collection. iocs (required): Indicators of Compromise (IOCs) to include in the collection. The items in the list can be domains, files, ip_addresses, or urls. At least one IOC must be provided. private: Indicates whether the collection should be private. Returns: A dictionary representing the newly created collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
descriptionYes
iocsYes
privateNo
api_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description bears full responsibility. It mentions the return value (a dictionary) and that at least one IOC is required. However, it does not disclose potential side effects (e.g., whether existing collections are overwritten) or authorization requirements. The transparency is adequate but not thorough.

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 concise and structured with Args and Returns sections. It front-loads the purpose and includes essential details. Minor improvements could be made by removing redundancy (the Args section repeats the description).

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?

The tool has an output schema, so the description's focus on input is appropriate. It covers most essential aspects, but omits constraints like maximum IOCs and does not clarify if the operation is synchronous or asynchronous. For a creation tool, additional context on success/failure states would be helpful.

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 adds significant meaning. It explains the types of IOCs (domains, files, ip_addresses, urls) and the purpose of the 'private' parameter. However, the 'api_key' parameter is not explained, leaving a gap.

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 creates a new collection in Google Threat Intelligence. It uses a specific verb ('creates') and resource ('collection'), distinguishing it from sibling tools that are primarily retrieval or analysis-focused.

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 includes a usage guideline: 'Ask for the collection's privacy... if the user doesn't specify.' This provides context on how to handle user input. However, it does not explicitly contrast with sibling tools or provide when-not-to-use instructions.

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