Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_file_hashes

Read-onlyIdempotent

Calculate complete cryptographic hashes for a workspace file within an engagement, choosing algorithms as needed to verify integrity and support evidence records.

Instructions

Calculate complete cryptographic hashes for a workspace file.

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_hashes"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
algorithmsNo
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 profile is covered. The description adds the notion of 'complete' hashing (full-file, all algorithms) which is genuinely useful context, but says nothing about cost on large files or how the default algorithm set is chosen.

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 front-loaded sentence with no filler; every word contributes. It is arguably too terse for the parameter surface, but there is no wasted wording to trim.

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?

An output schema exists, so return values need not be described, and the annotations cover safety. However, for a tool with three undocumented parameters including an algorithm selector, the description leaves the agent guessing about path format and default algorithm 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% across all three parameters, so the description carries the burden and largely fails: it never explains whether 'path' is workspace-relative, what 'engagement_id' scopes, or what happens when 'algorithms' is left null (presumably all algorithms, but that is only hinted by 'complete'). With a 0% coverage schema this is a real gap.

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 ('Calculate') and resource ('complete cryptographic hashes') scoped to 'a workspace file', which clearly separates it from a plain file-read tool like oc_file. It does not name or contrast any sibling, so the differentiation is inferred rather than stated.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as reading a file directly versus hashing it. The only implied guidance comes from the phrase 'workspace file', which merely restates the required parameter scope.

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