Skip to main content
Glama
threadlinqs-cmd

Intel Threadlinqs MCP

Search Detections

search_detections
Read-onlyIdempotent

Search detection rules by keyword to find detections matching specific topics like ransomware or lateral movement. Filter by type and severity for targeted results.

Instructions

Search detection rules by keyword — matches against detection names and descriptions. Filter by type and severity. WHEN TO USE: for finding detections by topic (e.g. 'ransomware', 'lateral movement', 'credential dumping'). To list every detection for a specific threat, use get_detections(threat_id=...) instead. Returns has_more/next_offset for paging.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoDetection language filter
limitNoMax results per page (default 25, max 200).
queryYesSearch term (matches detection name and description)
offsetNoPagination offset (0-based). Pass next_offset from the previous response to page through results.
severityNoSeverity level filter

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
countNo
has_moreNo
next_offsetNo
Behavior4/5

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds pagination details (has_more/next_offset), which is useful but not contradictory. Adequate for the annotation coverage.

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

Conciseness5/5

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

Extremely concise: two sentences plus a usage note. Front-loaded with purpose, no filler. Every sentence earns its place.

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 tool's complexity (5 params, output schema exists), description covers purpose, usage guidelines, and pagination. Agent has enough context to use it correctly without needing additional details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description adds minimal context beyond schema, mostly restating keyword matching and filtering. Does not compensate significantly, but no gaps.

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?

Description clearly states the tool searches detection rules by keyword, matching against names and descriptions, with filtering options. It also distinguishes from sibling tool get_detections by specifying when to use each.

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

Usage Guidelines5/5

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

Explicitly includes 'WHEN TO USE' guidance and provides alternative (get_detections(threat_id=...)) for listing detections for a specific threat. This helps the agent decide between 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/threadlinqs-cmd/intelthreadlinqs-mcp'

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