usom-mcp

Search Threats

search_threats

Read-only

Query Türkiye's USOM malicious-link list by keyword, type, category, source, or date range to retrieve matching threat records.

Instructions

Search the USOM list by keyword, type, category, source and date range.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_threats"
  }
}

Input Schema

Name	Required	Description
`type`	No	Indicator type.
`limit`	No	Page size (1-200).
`query`	No	Case-insensitive substring of the listed value.
`offset`	No	Records to skip.
`source`	No	Source code: US, SO, RS, IH or SB.
`date_to`	No	YYYY-MM-DD (whole day included) or with time.
`category`	No	Category code (PH, BP, ...).
`date_from`	No	YYYY-MM-DD or YYYY-MM-DD HH:MM[:SS], inclusive.
`connection_type`	No	Connection type code (AC, BC, EK, MC, MF, MM, OT, PH).
`max_criticality_level`	No	Keep records at this level or more critical (1 = max).

Output Schema

Name	Required	Description	Default
`note`	No
`cache`	Yes
`error`	No
`items`	Yes
`stale`	Yes	True when a refresh failed and cached data may be outdated; warn the user.
`offset`	Yes
`source`	No		T.C. Siber Güvenlik Başkanlığı / USOM (siberguvenlik.gov.tr)
`returned`	Yes
`data_origin`	Yes
`total_count`	Yes
`timestamps_timezone`	No		unspecified

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing behavioral beyond that—no pagination/default-limit behavior, no indication of result ordering or scope limits across the USOM list.

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?

One short sentence with the resource and filter axes front-loaded and no wasted words. It is efficient, though terseness here shades into under-specification rather than elegance.

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?

With an output schema present, return values need not be explained, and the schema fully covers parameters. However, for a 10-parameter open-world search tool, the description omits practical context such as paging behavior, default page size, and how it relates to sibling search tools.

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 description coverage is 100%, so all ten parameters are already documented with formats, enums and ranges (e.g., source codes, date formats, criticality direction). The description only gestures at the same filter axes, adding no syntax or semantics beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Search') and resource ('the USOM list') plus the filter axes it accepts. It is clear about what the tool does, but it never names or distinguishes itself from siblings like latest_threats, which also surface threat data.

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?

No when-to-use guidance is given: it does not say when to prefer this over latest_threats or the check_* lookup tools, nor when a search is inappropriate. The filter list implies usage but leaves the agent to infer routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server