Skip to main content
Glama

List files

list_files
Read-only

Files in the workspace library: uploads and generation outputs.

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_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. Beyond that, the description only reveals the composition of results (uploads plus generation outputs); it says nothing about ordering, default limit behavior, or whether limit caps the result set, which is the main behavioral question for a listing tool with a limit parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment with no wasted words, but the brevity comes at the cost of substance rather than from disciplined editing. There is no front-loaded verb or structured lead sentence to orient the agent.

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

Completeness2/5

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

An output schema exists so return values need no explanation, and annotations cover the read-only safety profile. Still, for a tool with an entirely undocumented parameter set (0% coverage), the description leaves the agent guessing how to filter and constrain results, which is more than a minor gap.

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% and the two parameters ('type' and 'limit') have no descriptions, enums, or constraints in the schema. The mention of 'uploads and generation outputs' faintly hints at the values 'type' might accept, but it never explains the parameter, its allowed values, or what limit=20 default implies, so the gap is largely unaddressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource and scope ('Files in the workspace library: uploads and generation outputs') and implicitly distinguishes the content from generation-only siblings like list_generations. However, it is a noun phrase with no verb, so it never states that it lists or retrieves these files; the action must be inferred from the tool name and title.

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 guidance on when to call this versus alternatives such as list_generations or get_upload, nor any note on prerequisites or when the result set would be empty. The only hint is the mention of uploads and generation outputs, which suggests coverage rather than routing.

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