Skip to main content
Glama
Sign In

hashn

by com.hashn
OverviewDiscussionsAdmin

get_file_link

Short-lived direct link to blob storage, for large or binary files. With path, returns file_url for that one file (GET to download; PUT with header 'x-ms-blob-type: BlockBlob' to upload when access='readwrite'); saves made with it are recorded under your name. Without path, returns container_url and sas_token for the whole workspace, read only (access='readwrite' needs a path). No link deletes: use delete_file. For files up to 3 MiB, write_file is simpler.

Input Schema

NameRequiredDescriptionDefault
pathNoOne file: the link then works for that file only (and saves made with it carry your name). Omit for a read link to the whole workspace.
accessNo'read' to download, or 'readwrite' to upload (needs a path).read
api_tokenNoYour hashn API token, if you can't send it as the 'Authorization: Bearer <token>' header. Omit it when the header is set.
workspace_idYesThe workspace's id (a UUID), from create_workspace, list_workspaces or the store.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / access / description
      Added value: +"'read' to download, or 'readwrite' to upload (needs a path)."
    • addedInput schema / properties / api_token / description
      Added value: +"Your hashn API token, if you can't send it as the 'Authorization: Bearer <token>' header. Omit it when the header is set."
    • addedInput schema / properties / path / description
      Added value: +"One file: the link then works for that file only (and saves made with it carry your name). Omit for a read link to the whole workspace."
    • addedInput schema / properties / workspace_id / description
      Added value: +"The workspace's id (a UUID), from create_workspace, list_workspaces or the store."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only give generic readOnly/destructive flags; the description adds the traits that matter: the link is short-lived, workspace-wide links are read-only, per-file readwrite links permit PUT uploads (with the exact required header), and saves are attributed to the caller. That is real behavioral context the annotations do not carry.

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?

Front-loaded with the core purpose, then structured by the two modes (with path / without path), then exclusions. Dense but every sentence carries information an agent needs.

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

Completeness5/5

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

No output schema exists, so the description usefully names the return values (file_url, container_url, sas_token) and explains how to use them. Combined with the sibling routing and mode branching, nothing needed to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds operational meaning beyond the schema: the PUT with 'x-ms-blob-type: BlockBlob' upload mechanism, the read-only constraint when path is omitted, and the attribution behavior of per-file links. It largely echoes the schema's path/access text, so it does not fully earn a 5.

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 (get a direct link to blob storage) and immediately scopes it to 'large or binary files', which separates it from read_file/write_file. An agent can identify the tool and its niche without opening the schema.

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

Usage Guidelines5/5

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

Explicitly routes alternatives: 'No link deletes: use delete_file' and 'For files up to 3 MiB, write_file is simpler', plus the condition that access='readwrite' needs a path. Both when-to-use and when-not-to-use are covered.

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

All hashn toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources