Skip to main content
Glama
maxkuminov

Obsidian MCP (pgvector + Ollama, self-hosted)

by maxkuminov

request_download

Generate a short-lived download link for a vault file so a human can save it. Handy for PDFs, images, or archives that a raw byte response cannot render.

Instructions

Get a short-lived link a person can use to save a vault file. Peer to read_file, which returns the bytes to you — use this one when the file is for the human, not for you.

Handy for anything read_file would waste context on or cannot render: a PDF, a large image, an archive. Reading works with a read-only key.

The token lives in the URL's # fragment, so it never reaches an access log. Treat the whole URL as a secret — whoever holds it can read that one file until it expires. Never put it in a query string.

The link is bound to the file as it is now: if it is edited or replaced, the link stops working rather than serving different content than you described. Unlike an upload link it can be used more than once, so the person can preview and then save.

From a shell: `curl -H "Authorization: Bearer " -o

Args: path: Vault-relative path of the file to share. expires_in: Seconds until the link dies. Clamped to 60–3600; defaults to TRANSFER_TOKEN_TTL_SECONDS (600).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
expires_inNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so richly: it discloses the token-in-#-fragment security property, the 'treat URL as secret' rule, expiry clamping (60-3600s, default 600), link invalidation on file edit/replacement, and multi-use behavior. No contradiction with annotations (none exist).

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?

The description is longer than average but every paragraph earns its place: purpose, usage scenarios, security warning, link-binding behavior, shell example, and parameter documentation. It is well-structured and front-loaded with the core message, with zero filler for a tool carrying security implications.

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?

The description covers the full workflow: when to use, security handling, expiry behavior, link singularity, multi-use property, a curl usage example, and both params. Given the tool's security-sensitivity and the available output schema, nothing material is left unexplained.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description fully documents both parameters: path is defined as 'Vault-relative path of the file to share' and expires_in as 'Seconds until the link dies. Clamped to 60-3600; defaults to TRANSFER_TOKEN_TTL_SECONDS (600).' This adds semantic value far beyond the bare schema types.

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?

The description states a specific purpose (get a short-lived link for a human to save a vault file) and explicitly distinguishes itself from read_file, which returns bytes to the agent. The 'peer to read_file' framing clearly differentiates the tool from its closest sibling.

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?

Explicit when-to-use guidance is given ('use this one when the file is for the human, not for you') plus concrete scenarios (PDFs, large images, archives where read_file would waste context). It also contrasts with read_file and upload links, naming alternatives. This is model guidance.

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/maxkuminov/obsidian-mcp'

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