Skip to main content
Glama
Sign In

Cactal

by ai.cactal
OverviewDiscussionsAdmin

List source files

websiteSourceCode_files_list
Read-onlyIdempotent

Lists file identities, sizes, and line counts without contents, sorted by type then name with cursor pagination (default 20, maximum 100). Filter by name with nameGlob. Defaults to head; pass target=published or an explicit version, and pin continuation requests to the resolved response version.

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": {
      "websiteId": "<websiteId>"
    },
    "name": "websiteSourceCode_files_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum files to return. Defaults to 20 and cannot exceed 100.
cursorNoOpaque cursor from the previous page. Continue with the returned resolved version to keep the listing pinned.
targetNoVersion alias to read: `head` (default) or `published`.
versionNoExplicit source version. Takes precedence over `target`.
nameGlobNoOnly list files whose name matches this glob. `*` and `?` stop at a `/` segment boundary; `**` crosses them, for example `blog/**`.
websiteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The safety profile is already carried by annotations (readOnlyHint, idempotentHint, destructiveHint=false), yet the description adds real value: contents are excluded, results are sorted by type then name, pagination bounds are 20/100, and iteration must be pinned to the resolved version. It doesn't describe the response envelope shape, but that is a minor omission.

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?

Three dense sentences with no filler and the payload description front-loaded before pagination, filtering, and version guidance. It is slightly packed with defaults and constraints that partly duplicate the schema, but nothing is wasted.

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

Completeness5/5

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

There is no output schema, and the description compensates by stating exactly what fields come back (identities, sizes, line counts, no contents) and the sort order. Combined with pagination and version-pinning rules, an agent has everything needed to call this correctly.

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 83%, so the schema already documents limit bounds, glob segment semantics, cursor pinning, and version/target precedence. The description restates limit defaults and the nameGlob/version behavior without adding syntax or edge-case detail beyond the schema, making 3 the appropriate baseline.

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 uses a specific verb and resource ('Lists file identities, sizes, and line counts without contents'), which clearly separates it from content-reading siblings like files_read. It does not name a sibling tool explicitly, which keeps it 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 Guidelines4/5

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

It states when head applies versus `target=published` or an explicit `version`, and gives concrete guidance to pin continuation requests to the resolved response version. It gives no guidance on when to prefer this over files_search or files_diff, so usage is clear but not exhaustive.

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

All Cactal toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources