Skip to main content
Glama

Dateien auflisten

fs_list
Read-only

Listet die Dateien eines Workspace mit Grösse und Prüfsumme.

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": {
      "website": "<website>"
    },
    "name": "fs_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNoUnterordner der Website, z. B. «img» – leer für alle Dateien.
websiteYesKennung oder Name der Website. Reicht der Zugang ueber mehrere Organisationen und gibt es die Kennung mehrfach, «organisation/website» schreiben.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results include size and checksum, which is genuine context about what the call yields. It says nothing about ordering, result caps, or whether a missing subfolder errors versus returns empty, so it stops short of rich behavioral disclosure.

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 no filler; the purpose and the returned fields appear immediately. It is efficient rather than padded, but the same brevity is what leaves the usage gaps, so it is not a 5.

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

Completeness3/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 partially compensates by naming the returned fields, but an agent still lacks any sense of result shape, ordering, or volume limits. The "Workspace" versus "website" wording mismatch and the absence of any scoping caveats leave the definition adequate but not complete for a listing tool.

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 100%, so both parameters are already documented in the schema, including the organisation/website disambiguation and the empty-string meaning for dir. The description adds no parameter detail beyond that, which is acceptable but earns only the baseline.

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 gives a specific verb plus resource ("Listet die Dateien eines Workspace") and names what comes back (size and checksum). It is clear what the tool does, though it never contrasts itself with fs_read or fs_delete, so the agent must infer the boundary from names alone. Minor terminology drift: the description says "Workspace" while the schema's required parameter is "website".

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 or when-not-to-use guidance at all. Nothing tells the agent to prefer this over fs_read for inspecting a single file, or to use it before fs_write/fs_delete to discover paths. The only implied usage comes from the verb "list".

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources