Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_file_triage

Triage a supplied engagement file offline for SHA-256, file identification, bounded strings and indicators without executing it, returning a persisted report path and stated analysis limits.

Instructions

Triage a supplied engagement file offline: complete SHA-256, file identification, bounded strings and indicators. Never executes the input; returns a persisted report path and explicit analysis limits.

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": {
      "engagement_id": "<engagement_id>",
      "path": "<path>"
    },
    "name": "oc_file_triage"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
max_bytesNo
engagement_idYes
min_string_lengthNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false and non-idempotency, and the description adds genuinely new behavior: the input is never executed, strings are bounded, the report is persisted to a path, and the analysis carries explicit limits. That said, it does not say where the report is persisted, whether repeats overwrite prior reports, or what the analysis limits actually are.

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?

A single dense sentence plus one clarifying clause, front-loading the action and following with the safety and return-value facts. No filler, though the colon-list and semicolon clause make it slightly harder to scan than it needs to be.

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?

Return values are backed by an output schema, so the mention of a persisted report path is sufficient there, and the no-execution guarantee covers the main safety question. However, with four undocumented parameters and a mutation-bearing tool (report writing), the definition leaves meaningful gaps in scoping and parameter behavior.

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

Parameters2/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 carry parameter meaning, and it largely does not. 'Bounded strings' faintly gestures at max_bytes and min_string_length, and 'supplied engagement file' at path, but engagement_id is never explained, defaults and units (bytes, characters) are untouched, and no parameter is named directly.

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?

Names a specific verb (triage) and resource (supplied engagement file) and enumerates the concrete outputs of the analysis: SHA-256, file identification, bounded strings, indicators. It does not explicitly differentiate itself from siblings such as oc_file_hashes or oc_file, so an agent must still infer the boundary, but the tool's own scope is unambiguous.

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: 'triage a supplied engagement file offline' suggests a first-pass static inspection, and 'never executes the input' implies safe handling of untrusted files. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g., hash-only vs. full triage), so the agent must infer selection criteria.

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