Skip to main content
Glama
threadlinqs-cmd

Intel Threadlinqs MCP

Get OSINT Corroboration

get_osint
Read-onlyIdempotent

Corroborate a threat ID or IOC against community OSINT data. Returns tags, indicator sightings, reporters, and linked threats, including whether the community saw the indicator before your report.

Instructions

Community corroboration for a threat or an indicator from the TL_OSINT_Scan layer (tweetfeed.live, CC0). Given threat_id, returns the matched community tags, the corroborated indicator count, and whether the community saw an indicator BEFORE our report. Given ioc_value, returns sightings, reporters, tags and every linked threat. Community-sourced and heavily concentrated (~73% of recent submissions come from a single reporter) — treat as corroborating evidence, never as authoritative attribution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ioc_valueNoExact indicator (IP, domain, URL, MD5 or SHA256). Returns the community lookup + our linked threats.
threat_idNoThreat ID (e.g. TL-2026-1531). Returns the per-threat corroboration block.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueNoPresent on the per-IOC shape (ioc_value input).
scannedNo
lead_daysNoDays the community saw an indicator before our report.
reportersNo
threat_idNoPresent on the per-threat shape.
threat_idsNo
corroboratedNo
matched_tagsNo
indicator_countNo
community_seen_before_reportNo
Behavior5/5

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

Beyond annotations, the description discloses the data source (tweetfeed.live, CC0), a concentrated submission pattern (~73% from a single reporter), and explicitly warns to treat results as corroborating evidence, never as authoritative attribution. This is valuable context that annotations do not provide.

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?

The description is three sentences, each earning its place: purpose, per-parameter behavior, and a reliability caveat. It is front-loaded with the core function and contains no filler.

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 simplicity (2 parameters, output schema provided), the description covers all necessary aspects: both usage modes, data provenance, and a critical reliability caveat. The output schema handles return value structure, so no gap exists.

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

Parameters5/5

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

The description adds return-field details beyond the schema's brief parameter descriptions: for threat_id it lists matched community tags, corroborated indicator count, and the BEFORE report flag; for ioc_value it lists sightings, reporters, tags, and linked threats. This significantly enriches the meaning of each parameter.

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 provides 'Community corroboration for a threat or an indicator from the TL_OSINT_Scan layer', with specific outputs for threat_id and ioc_value. This distinguishes it from sibling tools like get_osint_trends and get_ioc_intelligence by focusing on corroboration from a specific data source.

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 clearly implies when to use the tool (when community corroboration is needed) and describes behavior for each parameter. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to select it appropriately.

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