Skip to main content
Glama

post_fs_hash

Compute and return the cryptographic hash of a file or directory to verify data integrity and detect changes.

Instructions

Error codes: invalid_id, path_not_found, internal_error, disk_unavailable, invalid_request, invalid_conflict_mode, exec_failed, out_of_memory, task_not_found, invalid_state, invalid_task_type, destination_conflict, access_denied, disk_full, none, archive_read_failed, archive_open_failed, archive_write_failed, chdir_failed, dest_is_not_dir, file_exists, file_not_found, mkdir_failed, open_input_failed, open_output_failed, opendir_failed, overwrite_failed, path_too_big, repair_failed, rmdir_failed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

No annotations provided, and the description gives no behavioral details such as whether it modifies state, requires authentication, or its side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While short, the description is not conciseness but under-specification: it is a list of error codes with no explanation, making it useless.

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

Completeness1/5

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

The tool has an output schema (not shown), but without any description of purpose or behavior, the description is wholly inadequate for the agent to use the tool correctly.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though there are no parameters (schema coverage 100%), the description adds zero insight into what the tool does, leaving the agent completely uninformed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description only lists error codes and does not state what the tool does. It fails to convey that 'post_fs_hash' likely computes a hash of a file or path.

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

Usage Guidelines1/5

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

No guidance on when to use this tool versus other post_fs_* tools (e.g., post_fs_cat, post_fs_cp) or any context about prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nelson-PROIA/freebox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server