Skip to main content
Glama

List Storage Files

list_storage_files
Read-onlyIdempotent

[read] The folders and files directly inside a folder of a storage account (storages_account_id or storages_account_uuid; path, empty = zone root). Each file has its name, length, content_type, cdn_url and description (null when it has none).

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": "list_storage_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
storages_account_idNo
storages_account_uuidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description correctly spends its words elsewhere: it discloses the per-file return shape (name, length, content_type, cdn_url, description) and notes that description is null when absent. It does not discuss pagination or ordering of results, which for a directory listing would be useful.

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?

Two dense sentences with the scope constraint front-loaded and no filler; the parenthetical packing of parameter hints is slightly awkward but efficient. Every clause carries information.

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 does the right thing by enumerating return fields, and it explains root-path semantics. However, for a tool where all three parameters are optional, it leaves unclear what a bare call returns and how path strings should be formatted, which is a meaningful gap.

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 coverage is 0%, so the description must carry the burden. It does add real meaning – 'path, empty = zone root' and that either account id or uuid identifies the account – but it never says whether path is a slash-delimited path or a single folder name, nor what happens when all three optional params are omitted.

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 concrete resource (folders and files) and a precise scope ('directly inside a folder', i.e. non-recursive) of a storage account, so the agent knows exactly what comes back. It stops short of naming sibling list tools such as list_storage_remote_files or list_storages_accounts to differentiate.

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

Usage Guidelines3/5

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

Usage is only implied by the '[read]' tag and the word 'list' – there is no explicit statement of when to call this rather than list_storages_accounts (to find an account) or list_storage_remote_files. No exclusions or prerequisites are given.

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.