Skip to main content
Glama

Modellix Media Generation

modellix_list_files

Read-onlyIdempotent

List the current team's uploaded files with pagination. Reuse existing file URLs where appropriate; defaults may retain files for 7 days.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds a lifecycle note (files may be retained 7 days by default) and mentions pagination, but the retention sentence is hedged and ambiguous about which "defaults" apply. No contradiction with annotations.

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?

Two short sentences with no filler, but the second sentence is muddled: "Reuse existing file URLs" is unclear in a listing context and the 7-day retention clause is vague. Brevity is fine; clarity of the second sentence is not.

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?

An output schema exists, so return values need not be described, and the tool is structurally simple. However, the undefined pagination parameters and the ambiguous retention/URL-reuse sentence leave real gaps for an agent deciding how to page and what to expect over time.

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 (limit, offset) carry only defaults and min/max constraints with no prose. The description's single word "pagination" signals that these are page controls but does not explain units, defaults, or the 100-item cap, so it does not compensate for the coverage gap.

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 ("List the current team's uploaded files") plus the pagination dimension, which cleanly separates it from siblings like modellix_list_models, modellix_upload_file, and modellix_delete_file. It does not explicitly name an alternative, so it falls just short of a 5.

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 statement of when to call this versus related tools such as delete_file or upload_file. "Reuse existing file URLs where appropriate" is guidance about caching, not about selecting this tool, and it is too vague to act on.

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.