Full tool catalog with args and returns·View as Markdown

MCP tools

Tools wrap shared v1 logic (not HTTP loopback). Unless noted, workspaceId defaults to the API key's workspace.

ToolScopeMaps to
list_workspacesworkspaces:readGET /workspaces
list_bucketsbuckets:readGET .../buckets
list_filesfiles:readlist + optional search/semantic
get_filefiles:readGET .../files/{fileId}
search_filesfiles:readkeyword + semantic
similar_filesfiles:readsimilar neighbors
ask_agentagent:runbucket agent
update_filefiles:writetags / description
get_intelligenceintelligence:readconfig + progress
start_backfillintelligence:writestart / resume / pause
presign_downloadfiles:downloaddownload URL
presign_uploadfiles:uploadupload URL
create_folderfiles:writemkdir

Common args

Most bucket tools take:

  • bucketId (required)
  • workspaceId (optional; defaults to key workspace)

list_files / search_files

  • prefix?, parentPrefix?, search?, tag?
  • semantic? (boolean)
  • limit?, offset?

ask_agent

  • query (string)

update_file

  • fileId, tags?, description?

start_backfill

  • action: start | pause
  • estimateToken? (required for start)

presign_upload

  • key, contentType?

presign_download

  • key? or fileId?

create_folder

  • key (folder path)

Resources

Doc markdown is exposed as MCP resources (file.rocks://docs/... and/or https .md URIs) so clients can pull API/MCP docs as context.

Errors

Missing scope or bucket allowlist → tool error with a clear message (same semantics as REST 403).

MCP tools · file.rocks docs