OwlMem

kb_file_get

Read-onlyIdempotent

Get a file from your space's file storage: text up to 100 KB comes back as is; bigger or binary files come back as a download URL valid for 15 minutes (curl -o from a shell). Use it for attachments on messages too.

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": "kb_file_get"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	true: always give a download URL instead of the content
`path`	Yes	Path in file storage (from kb_file_list or a message's attachments)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds real behavioral facts they don't: the 100 KB inline threshold, that larger or binary files are converted to a 15-minute download URL, and that it can be fetched with curl -o. That is exactly the context an agent needs before consuming the result.

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 sentences, front-loaded with the core action and its return shapes, with no filler. The threshold, URL expiry and attachment use case all earn their place.

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?

For a two-parameter read tool with no output schema, the description fully characterizes what comes back and in what form, including the escape hatch for forcing a URL. Nothing an agent needs to invoke 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 the baseline is 3. The description goes beyond it by explaining the default size-dependent behavior that the `url` flag overrides and by stating the URL's 15-minute validity, giving the boolean parameter practical meaning rather than just restating it.

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 and resource ('Get a file from your space's file storage') and immediately describes the two possible outcomes, which separates it cleanly from kb_file_list, kb_file_put and kb_file_delete. An agent can tell it is the single-file retrieval tool 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 Guidelines4/5

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

'Use it for attachments on messages too' gives a concrete non-obvious usage case beyond generic file retrieval. There are no explicit exclusions or named alternatives in the description itself, so it stops short of a full when/when-not statement.

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

All OwlMem tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?