Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Show Watched Folders

watched_folders
Read-onlyIdempotent

Lists a pod's folders whose new files are uploaded as Asset Hub assets, showing include patterns, enabled state, blocked reasons, revision, and editability.

Instructions

Show a pod's watched folders: folders whose new files are uploaded as Asset Hub assets. Each folder has origin (template or user), enabled, its include patterns and blocked_reason (network_storage = on network storage, nested_volume = overlaps your volume; never watched). revision is what set_watched_folders needs as expected_version; editable false (with a reason) means it can't be changed now. Reason no_sidecar means the pod has no uploader: when can_enable_saving is true, update_pod with enable_folder_saving=true adds it (one restart); otherwise the pod first needs storage (update_pod volumes/local_volumes).

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": {
      "pod": "<pod>"
    },
    "name": "watched_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
podYes
workspaceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), yet the description adds substantial behavioral context beyond them: what `blocked_reason` values mean (network_storage vs nested_volume, never watched), that `editable: false` means it can't be changed now, and that no_sidecar indicates a missing uploader with two distinct remediation paths. That is exactly the kind of mutation-adjacent consequence an agent needs before calling a read tool.

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 purpose, then ordered by field semantics and finally by remediation path; backticked identifiers make it scannable. It is dense and sentence three packs several conditions into one line, but no sentence is filler.

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

Completeness5/5

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

An output schema exists, yet the description usefully explains the meaning of key returned fields and what to do with them, and it spells out both blocked-state remediations. The only real gap is the undocumented `workspace` parameter, which is minor relative to the otherwise complete behavioral picture.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, but it only implicitly identifies `pod` ('a pod's watched folders') and never mentions `workspace` at all. With no enum/format details and one of two parameters entirely undocumented, the agent must open the schema and guess at `workspace` semantics.

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 first sentence names a specific verb and resource ('Show a pod's watched folders') and immediately defines the concept ('folders whose new files are uploaded as Asset Hub assets'). It also names related siblings (set_watched_folders, update_pod), so an agent can place it in the workflow without inspecting the schema.

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 description gives clear downstream routing: the returned `revision` is what set_watched_folders needs as `expected_version`, and blocked/no-sidecar cases route to update_pod with enable_folder_saving=true or storage changes. It does not explicitly say when *not* to call it or name a read-side alternative, but the workflow context is unambiguous.

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