Skip to main content
Glama

list_files

Lists workspace files in a remote Blender session, excluding internal state, with path, limit, and offset controls for browsing project files.

Instructions

List up to 1000 workspace files, excluding internal state.

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": {
      "session_id": "<session_id>"
    },
    "name": "list_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
limitNo
offsetNo
session_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It adds two useful facts — an internal-state exclusion and a 1000-item ceiling — but says nothing about ordering, pagination interaction between limit/offset, permissions, or what a truncated result looks like.

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?

One front-loaded sentence with no filler and no repetition of the name. The 'up to 1000' clause is mildly redundant with the schema's default/maximum but reinforces the result-set size for an agent skimming.

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?

Output schema exists, so return shape needn't be explained, but with zero annotation coverage, zero schema parameter descriptions, and a required session_id, the definition leaves the agent guessing about pagination strategy and path semantics. For a 4-parameter listing tool this is a thin definition.

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% across 4 parameters, so the description must compensate and largely does not. It only hints at the limit parameter's ceiling ('up to 1000'), which the schema already enforces via maximum: 1000; path, offset, and the required session_id receive no explanation of format or meaning.

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 ... workspace files') plus a scope qualifier ('excluding internal state'), so an agent can tell it apart from mutation siblings like upload_file. It stops short of naming or contrasting with list_checkpoints/list_sessions, so the differentiation is implied rather than explicit.

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 guidance, no prerequisites, and no mention of alternatives such as list_checkpoints or list_sessions. The agent must infer that this is the file-enumeration path for a workspace.

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