Tool Details: dlfs_read

Basic Information

Tool Name:dlfs_read
Asset Name:Read DLFS File
Description:Read a file from a DLFS drive. The 'mode' parameter controls how the file is returned: 'auto' (default) returns UTF-8 text for text files, or a reference with a WebDAV URL for binaries; 'text' forces UTF-8 decoding; 'bytes' returns base64-encoded bytes; 'json' parses the file as JSON and returns the value. For binary files, prefer fetching via the WebDAV GET transport at /dlfs/{drive}/{path} rather than using 'bytes' mode.
Adapter:dlfs
Asset Hash:0x6575b482b1113d88f649381bb06178e0a49d1ae17b6aefcf70f781e60001acb7
Input
PropertyTypeDescription
path*stringFile path within the drive
drive*stringDrive name
modestringHow to decode the file. Default 'auto'.
Output
PropertyTypeDescription
valueanyParsed JSON value (present for mode=json only).
sizeintegerSize in bytes
encodingstring'utf-8', 'base64', or 'binary'. 'binary' means bytes were not inlined — fetch via the 'url' field.
urlstringWebDAV URL to fetch raw bytes (present when encoding=binary)
mimestringBest-guess MIME type
contentstringFile content (present for modes auto/text/bytes). Text for utf-8 encoding, base64 for bytes.

MCP Tool Usage Examples

This tool can be called via the MCP (Model Context Protocol) endpoint. Here are examples of how to use it:

JSON-RPC Call Example:

POST to https://venue-3.covia.ai/mcp

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "dlfs_read",
    "arguments": {
      "input": "your input here"
    }
  }
}
cURL Example:
curl -X POST https://venue-3.covia.ai/mcp \\
  -H "Content-Type: application/json" \\
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "dlfs_read",
      "arguments": {
        "input": "your input here"
      }
    }
  }'
Python Example:
import requests
import json

url = "https://venue-3.covia.ai/mcp"
payload = {
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
        "name": "dlfs_read",
        "arguments": {
            "input": "your input here"
        }
    }
}

response = requests.post(url, json=payload)
result = response.json()
print(result)
JavaScript/Node.js Example:
const fetch = require('node-fetch');

const url = 'https://venue-3.covia.ai/mcp';
const payload = {
    jsonrpc: '2.0',
    id: 1,
    method: 'tools/call',
    params: {
        name: 'dlfs_read',
        arguments: {
            input: 'your input here'
        }
    }
};

fetch(url, {
    method: 'POST',
    headers: {
        'Content-Type': 'application/json'
    },
    body: JSON.stringify(payload)
})
.then(response => response.json())
.then(data => console.log(data));

Asset Metadata

{
  "name": "Read DLFS File",
  "description": "Read a file from a DLFS drive. The 'mode' parameter controls how the file is returned: 'auto' (default) returns UTF-8 text for text files, or a reference with a WebDAV URL for binaries; 'text' forces UTF-8 decoding; 'bytes' returns base64-encoded bytes; 'json' parses the file as JSON and returns the value. For binary files, prefer fetching via the WebDAV GET transport at /dlfs/{drive}/{path} rather than using 'bytes' mode.",
  "creator": "Covia",
  "operation": {
    "adapter": "dlfs:read",
    "toolName": "dlfs_read",
    "input": {
      "type": "object",
      "properties": {
        "drive": { "type": "string", "description": "Drive name" },
        "path": { "type": "string", "description": "File path within the drive" },
        "mode": { "type": "string", "enum": ["auto", "text", "bytes", "json"], "description": "How to decode the file. Default 'auto'." }
      },
      "required": ["drive", "path"]
    },
    "output": {
      "type": "object",
      "properties": {
        "content": { "type": "string", "description": "File content (present for modes auto/text/bytes). Text for utf-8 encoding, base64 for bytes." },
        "value": { "description": "Parsed JSON value (present for mode=json only)." },
        "encoding": { "type": "string", "description": "'utf-8', 'base64', or 'binary'. 'binary' means bytes were not inlined — fetch via the 'url' field." },
        "size": { "type": "integer", "description": "Size in bytes" },
        "mime": { "type": "string", "description": "Best-guess MIME type" },
        "url": { "type": "string", "description": "WebDAV URL to fetch raw bytes (present when encoding=binary)" }
      }
    }
  }
}

Navigation

Back to adapter details

Back to all adapters

Back to index