Skip to main content
Glama

fs_stat

Read-onlyIdempotent

Get metadata for a file or directory without downloading the contents. Returns path, name, type, size_bytes, content_type, visibility, version, created_at, and updated_at; a file in a declared file collection also returns collection, group (member collections) and owner_subject_id. File tools act with your developer authority over every file in the project.

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": {
      "project_id": "<project_id>",
      "path": "<path>"
    },
    "name": "fs_stat"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFull path with leading slash
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety bar is low, but the description adds real context: the full set of returned fields, the conditional collection/group/owner fields, and the authority model ("act with your developer authority over every file in the project"). That authority sentence is meaningful for an agent reasoning about scope, though permission prerequisites for private files aren't addressed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and its key differentiator, followed by the return-field inventory and then the authority note. The field enumeration is long but earns its place because no output schema exists; only minor tightening would improve it.

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?

With no output schema, the description usefully enumerates return fields and flags the conditional collection fields, which an agent would otherwise not anticipate. Missing only a note on failure behavior for nonexistent paths, which matters for a stat-style tool.

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 coverage is 100%, and both parameters carry their own substantive descriptions including the 'default' project_id shortcut and leading-slash path convention. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 metadata for a file or directory") and immediately scopes it with "without downloading the contents," which separates it from fs_read's content retrieval. An agent can pick between fs_stat and the read siblings from this sentence alone.

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?

The "without downloading the contents" qualifier makes the intended use case clear — checking type, size, or existence before deciding to read, write, or delete. It never names fs_read explicitly as the content-fetching alternative, and gives no exclusions, so it falls just short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources