Skip to main content
Glama
Sign In
bounded-filesystem-mcp

bounded-filesystem-mcp

by shivam-bit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get File Info

get_file_info
Read-only

Retrieve detailed file or directory metadata—size, creation and modification times, permissions, and type—without reading content. Works only within allowed directories.

Instructions

Retrieve detailed metadata about a file or directory. Returns comprehensive information including size, creation time, last modified time, permissions, and type. This tool is perfect for understanding file characteristics without reading the actual content. Only works within allowed directories.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description still adds value by enumerating what metadata is returned and flagging the sandbox constraint ('Only works within allowed directories'). It doesn't mention error behavior for nonexistent paths or symlinks, which keeps it short of a 5.

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?

Three sentences, front-loaded with the core action and the return contents, with no redundancy. The promotional phrasing 'This tool is perfect for' is the only slightly wasteful element.

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 lists the returned metadata fields, and it discloses the allowed-directory restriction. For a single-parameter read tool that is essentially complete; only path format and error semantics are left implicit.

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?

There is only one parameter (path) with 0% schema description coverage, so the description carries the burden. The 'allowed directories' constraint partially informs path validity, but it never says whether the path may be relative or must be absolute, nor what happens for invalid paths.

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?

Specific verb ('Retrieve') plus resource ('detailed metadata about a file or directory'), with an explicit enumeration of the fields returned (size, times, permissions, type). The clause 'without reading the actual content' distinguishes it from the read_file/read_text_file siblings.

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?

'This tool is perfect for understanding file characteristics without reading the actual content' implies the usage context, but no sibling is named and no when-not condition is given (e.g., use list_directory_with_sizes for bulk listings). Usage is inferred rather than stated.

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

Deploy Server

Other Tools