Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Path Info

get_path_info

Retrieves detailed filesystem metadata for a specified path—including type, size, owner, permissions, timestamps, symlink target, and access flags—to support debugging and security review.

Instructions

Detailed stat info: type, size, owner, permissions, times, symlink target, access flags.

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_path_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does hint that symlinks are reported via 'symlink target' rather than silently followed, which is useful, but it says nothing about what happens for a nonexistent or unreadable path (error vs. empty result), whether permissions are required, or that the operation is read-only and side-effect free.

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?

A single front-loaded sentence with a dense field list and no filler. The awkward line break and lack of a leading verb are minor blemishes on otherwise efficient phrasing.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with an output schema, the description's entire content is a restatement of return fields, which is partially redundant, while the aspects the structured data cannot convey -- usage context and error behavior on missing/inaccessible paths -- are absent and annotations are empty.

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 description must compensate for the single 'path' parameter, and it does not address it directly. However, the single required parameter is named 'path' and the enumerated metadata (owner, permissions, symlink target, access flags) makes clear it is a filesystem path, leaving little ambiguity about what to supply.

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 names a specific resource (a path) and enumerates exactly what is reported about it: type, size, owner, permissions, times, symlink target, access flags. That lets an agent distinguish a stat-style inspection from sibling tools like path_exists or copy_path without opening the schema, though the verb itself must be inferred from the name.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing tells the agent to prefer this over path_exists for a simple existence check, or when the metadata payload justifies the call. No preconditions, no exclusions, no alternatives are mentioned.

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