DNS-DATA Remote

file_info

Read-onlyIdempotent

Retrieve filesystem metadata about a remote file or directory. device_id identifies an authorized online device; path identifies an item on it. Read-only. Use before move_path, delete_path or write_file to inspect the target.

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": {
      "device_id": "<device_id>",
      "path": "<path>"
    },
    "name": "file_info"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`device_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4/5.0

Behavior3/5

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

The 'Read-only' statement merely restates readOnlyHint=true/destructiveHint=false, and idempotency is left to annotations. What the description does add beyond structured fields is the prerequisite that device_id must reference an 'authorized online device,' which is meaningful operational context. No return-format or failure behavior is described.

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?

Three tight sentences with no filler: purpose first, parameter glosses second, usage routing last. Every sentence carries distinct information.

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

Completeness4/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 and rich annotations, the description covers purpose, prerequisites, and usage context. The main gap is what metadata fields are actually returned, which an agent may want before chaining into move_path or delete_path.

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

Parameters3/5

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

Schema description coverage is 0%, so the schema names both parameters without explaining them; the description compensates by glossing device_id as an authorized online device and path as an item on it. However, it gives no format guidance (absolute vs relative path, separators), so compensation is only partial.

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 ('Retrieve filesystem metadata about a remote file or directory'), which naturally separates it from siblings like read_file (contents) and list_files (enumeration). The 'remote' scope and metadata framing make the tool's identity unambiguous.

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?

Explicitly routes the agent: 'Use before move_path, delete_path or write_file to inspect the target,' naming concrete alternatives and the condition that selects this tool. It stops short of a full when-not clause (e.g., why not list_files or read_file instead), but the guidance is clear and actionable.

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

All DNS-DATA Remote 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?