Skip to main content
Glama

File or folder metadata

nas_file_stat
Read-only

Retrieve file type, size, and Unix timestamps for one or more NAS paths, with per-path results so a missing path does not stop others.

Instructions

Get type, size and timestamps for one or more paths. The result always has items[], one per path in the order given; check each item for success, because one missing path does not stop the others. size and the time fields are strings; times are Unix seconds. The mode field is unreliable on existing paths, so do not use it to decide whether something is readable or writable.

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": {
      "paths": "<paths>"
    },
    "name": "nas_file_stat"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYesPaths to inspect. Absolute NAS paths (1 to 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/destructive annotations, the description discloses partial-failure semantics ('one missing path does not stop the others'), result ordering and cardinality ('items[], one per path in the order given'), and an explicit reliability caveat that the mode field must not be used to judge readability or writability. That last warning is exactly the kind of non-obvious trap annotations cannot express.

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?

Four tight sentences, each carrying distinct information: purpose, return shape, field typing, and the mode caveat. No filler, and the most important operational warning about the unreliable mode field is placed where it will be read before acting on results.

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?

There is no output schema, yet the description covers the return envelope (items[]), per-item success checking, value typing (strings, Unix seconds), and a field-level reliability warning. For a one-parameter read tool this leaves nothing an agent needs 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% and the single paths parameter is already documented as absolute NAS paths, 1 to 50. The description still adds value by tying input order to output order and clarifying that partial success is expected, which shapes how the agent should construct and interpret the array.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Get type, size and timestamps for one or more paths.' An agent knows exactly what comes back. It does not name a sibling such as nas_file_list or nas_file_find, so the reader must infer when metadata-only is preferable to listing or searching.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied rather than stated: batching up to 50 paths and the note that one missing path does not stop the others both hint at bulk stat workflows. There is no explicit when-to-use or when-to-prefer-an-alternative guidance against nas_file_find or nas_file_list, leaving the routing decision to the agent.

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