Sora Commander

Overview Schema Source Related Servers Discussions Admin

sha256_file

Computes the SHA-256 hash of an approved existing file without reading full contents into chat or altering permissions, so you can verify file integrity within configured roots.

Instructions

Stream a bounded file hash, with no install/execute permissions.

Use to compute the SHA-256 of an approved existing file without reading full contents into chat or changing permissions. Hash alone does not establish a trusted signature.

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

Input Schema

Name	Required	Description	Default
`path`	Yes	Path to the target within the already-configured Owner read/edit roots; path alone grants no access.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Nov 9, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful traits: streaming/bounded hashing, no install or execute permission grants, no permission mutation, and the caveat that a hash is not a signature. It does not cover behavior on a missing/unreadable path or error signaling, which matters for a security-sensitive operation.

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?

Two short sentences, front-loaded with the operation and immediately followed by the use case and the key limitation. No filler, and the trust caveat is placed where the agent will read it before acting.

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 single-parameter read-only hash tool with an output schema available, the description covers purpose, permission posture, and interpretation limits adequately. Error and preconditions (file must exist and be readable) are left implicit.

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% and the single 'path' parameter is already documented as being constrained to configured Owner read/edit roots. The description adds only a light 'approved existing file' qualifier, essentially restating the schema's access constraint, so baseline 3 applies.

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?

States a specific verb+resource ('compute the SHA-256 of an approved existing file') and explicitly carves out what it is not: it does not read full contents into chat and does not touch permissions, which separates it from siblings like read_text_file or compare_text_files.

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

Usage Guidelines4/5

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

'Use to compute the SHA-256 of an approved existing file without reading full contents into chat or changing permissions' gives clear context for selection, and 'Hash alone does not establish a trusted signature' sets a boundary on what the result proves. It stops short of naming a concrete alternative tool for verification, so it is clear but not fully routing.

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