Cactal

Read source files

websiteSourceCode_files_read

Read-onlyIdempotent

Reads up to 50 files by name from head, published, or an explicit version. A single-file read supports line and character ranges; continue truncated reads with nextStartCharacter and the resolved 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>",
      "names": "<names>"
    },
    "name": "websiteSourceCode_files_read"
  }
}

Input Schema

Name	Required	Description
`names`	Yes	File names to read (up to 50). Singleton files are addressed by their type name, for example `global_css`.
`target`	No	Version alias to read: `head` (default) or `published`.
`endLine`	No	Last line to return (1-based, inclusive). Only valid when reading a single file.
`version`	No	Explicit source version. Takes precedence over `target`.
`startLine`	No	First line to return (1-based, inclusive). Only valid when reading a single file.
`websiteId`	Yes
`endCharacter`	No	Last character to return from the selected line range (1-based, inclusive). Only valid when reading a single file.
`startCharacter`	No	First character to return from the selected line range (1-based, inclusive). Only valid when reading a single file.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With annotations already declaring a safe, idempotent read, the description adds genuinely useful behavior: truncation handling via `nextStartCharacter` and the resolved `version`, plus the constraint that line/character ranges only apply to single-file reads. It stops short of describing error conditions (e.g., missing files, mixed multi-file/range requests).

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?

Two compact sentences, front-loaded with the core operation and followed by the single-file/continuation caveat. No filler.

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?

For a read-only tool with annotations, high schema coverage, and no output schema, this is largely sufficient: it covers sources, batching, ranges, and continuation. Minor gaps remain around what is returned for partial failures and how multi-file requests interact with ranges beyond the single-file note.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 88%, so most parameters are already documented. The description still adds meaning by explaining the multi-file vs. single-file distinction and tying `version` to continuation after truncation, which the schema does not fully convey as a workflow.

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 gives a specific verb and resource ('Reads up to 50 files by name') and pins the source scope to head, published, or an explicit version. It does not name a sibling, but 'by name' implicitly separates it from files_list and files_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied through the source options (head/published/version) and the note that ranges apply to single-file reads. However, there is no explicit guidance on when to choose this tool over files_list, files_search, or files_diff, so the agent must infer the selection.

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

All Cactal tools Inspect

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

Need Help?