Skip to main content
Glama

security-crypto

ioc_defang_and_refang

Safely defang or refang malicious IOC URLs, domains, email addresses, and IPv4 indicators (hxxp://, [.], [@]) for SOC reports.

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": "ioc_defang_and_refang"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNodefang
textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it only partially does. 'Safely' hints that indicators are not resolved or fetched (a purely local text transformation), which is meaningful context, but it never states whether multiple indicators can be passed at once, what the output looks like, or how malformed input is handled.

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?

One sentence, front-loaded with the action and resource types, with the use case at the end. Nothing is redundant and the parenthetical examples add concrete value rather than padding.

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?

For a two-parameter, non-destructive transformation tool with no output schema, the definition covers what is transformed and why, which is most of what an agent needs. The remaining gaps are modest: input cardinality and output format are unstated, but neither is likely to cause a misinvocation.

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 0%, so the description must compensate. It helps by naming the escaped representations (hxxp://, [.], [@]) that define the defang/refang transform, but it never explains the 'text' parameter's expected shape (single indicator vs. list) or explicitly ties 'mode' to direction of transformation, leaving the enum to speak for itself.

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 gives a specific verb pair (defang/refang) and enumerates the exact resource types handled: IOC URLs, domains, email addresses, and IPv4 indicators, with the target output context (SOC reports). No sibling tool in the catalog performs this transformation, so an agent can identify it unambiguously from the name plus this sentence.

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?

The purpose clause 'for SOC reports' implies the appropriate context, but there is no explicit when-to-use/when-not guidance and no direction on choosing between the two modes beyond the default. Since no sibling covers this operation, the lack of alternatives is acceptable, but the agent is left to infer that raw, unescaped indicators should be passed for defang and escaped ones for refang.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources