Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_extract_indicators

Read-onlyIdempotent

Extract URLs, IPv4 addresses, CVEs, and common hashes from supplied text to quickly identify indicators of compromise.

Instructions

Extract URLs, IPv4 addresses, CVEs, and common hashes from supplied text.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "oc_extract_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and determinism profile is fully covered structurally. The description adds the extraction scope (which IOC classes are returned), which is genuinely useful behavioral content, but says nothing about deduplication, ordering, or handling of text with no matches.

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?

A single front-loaded sentence with the verb first and the output classes enumerated; no filler, no restatement of the name or title.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and a one-parameter, read-only extractor is intrinsically simple. The only meaningful omission is boundary-setting on what indicator types are excluded and how the text input is treated, which would help an agent avoid misusing it as a general IOC scraper.

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?

There is a single parameter, 'text', with 0% schema description coverage. The description's phrase 'from supplied text' effectively tells the agent the parameter is the free-text blob to scan, which compensates for the undocumented schema, but it adds no detail on size limits, encoding, or multi-line handling.

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?

The description gives a specific verb ('Extract') and enumerates the exact resource types ('URLs, IPv4 addresses, CVEs, and common hashes') plus the input medium ('supplied text'). An agent knows precisely what the tool produces, though it doesn't differentiate from any sibling (none of the listed siblings clearly overlap, so this is a minor gap).

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

Usage Guidelines3/5

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

Usage is only implied: the phrasing 'from supplied text' signals the tool needs raw text in hand, and the enumerated indicator types imply the scope of use. There is no explicit when-to-use/when-not guidance, no mention of what is NOT extracted (e.g., domains, emails, file paths), which is the most likely agent mistake.

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

Deploy Server

Other Tools