Skip to main content
Glama
Sign In
mega-mcp

mega-mcp

by Anicodeth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Browse a MEGA folder

mega_browse

List files and folders in a public MEGA folder. Use path to scope into subfolders or recursive to walk entire tree. Returns name, path, type, and size.

Instructions

List files and folders in a public MEGA folder link. Use recursive to walk the entire tree, or path to scope into a subfolder. Returns name, path, type, and size for each entry.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mega_browse"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkNoPublic MEGA folder/file link. Defaults to MEGA_LINK env.
pathNoSubfolder path within the link to list, e.g. 'docs/2024'.
recursiveNoList the full tree under the path (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, but description discloses read-only behavior (list), output fields, and parameter effects. Adequate transparency for a listing tool.

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?

Three concise sentences: purpose, parameter usage, and output. Front-loaded with no wasted words.

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?

Covers essential output fields. Lacks mention of error handling or pagination, but sufficient for a folder listing tool with sibling differentiation.

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 covers all parameters with descriptions; description adds context on usage (recursive for tree, path for subfolder). Adds value beyond schema.

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?

Clearly states verb 'List' and resource 'files and folders in a public MEGA folder link'. Distinguishes from siblings like mega_read_file and mega_search by specifying listing a folder's contents.

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?

Provides guidance on parameters: 'Use recursive to walk the entire tree, or path to scope into a subfolder.' Does not explicitly exclude alternatives but implies usage scope.

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