Skip to main content
Glama
Sign In
Egnyte Large File Manager

Egnyte Large File Manager

by hschickdevs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Egnyte: file metadata

egnyte_stat
Read-only

Retrieve file metadata including size, checksum, and folder status. Check before downloading to confirm it is a file and review its size.

Instructions

Get metadata for an Egnyte file or folder (size, checksum, ids, is_folder). Use before downloading to check size / that it is a file.

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": {
      "egnyte_path": "<egnyte_path>"
    },
    "name": "egnyte_stat"
  }
}

Input Schema

NameRequiredDescriptionDefault
egnyte_pathYesEgnyte path to inspect

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, and the description adds specific returned fields (size, checksum, ids, is_folder) and usage hint. No contradictions.

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?

Two sentences with no filler: first defines purpose, second gives usage guidance. Efficient and well-structured.

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?

Simple tool with one param and no output schema; description covers returned fields and use case. Could mention return format but not necessary for completeness given context.

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?

Only one parameter egnyte_path with 100% schema coverage; description does not add extra meaning beyond the schema, but baseline is acceptable.

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?

The description clearly states 'Get metadata for an Egnyte file or folder (size, checksum, ids, is_folder)' with a specific verb and resource. It also differentiates from sibling tools like egnyte_download by suggesting use before downloading.

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 advises to 'Use before downloading to check size / that it is a file', providing clear context for when to use. Lacks explicit exclusions or alternatives, but sufficient given sibling tools.

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