Skip to main content
Glama

get_all_files

Read-onlyIdempotent

Lista todos los archivos subidos al workspace (adjuntos a documentos). Retorna: id, file_name, file_url, file_size (bytes), mime_type, document_id, created_at. Para ver el uso total de storage: usar get_storage_usage.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo (default: 50)
offsetNoOffset para paginación
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds a useful enumeration of returned fields (including file_size in bytes), which matters since there is no output schema, but says nothing about result ordering or pagination behavior.

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 tight sentences: scope first, return payload second, alternative last. Nothing is redundant and the alternative is placed where an agent would look after deciding the tool lists files.

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?

No output schema exists, and the description compensates by listing the returned fields; pagination and workspace scoping are covered by the schema and annotations. It is nearly complete, lacking only ordering/total-count expectations for a paginated list.

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% and the schema already explains limit, offset and the workspace_id UUID-or-name convention including the omit-to-get-all behavior. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ("Lista todos los archivos subidos al workspace") and narrows the scope with "(adjuntos a documentos)". It does not explicitly contrast with the sibling get_document_files, which is the closest-sounding alternative, so differentiation is only implicit via the word "todos".

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?

Gives one explicit routing rule: for total storage consumption use get_storage_usage instead. The other natural alternative, get_document_files (files of one document), is never mentioned, so an agent must infer that this tool is the broad listing.

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