Skip to main content
Glama

read_file

Reads the full text content of a file on a cPanel server, with an optional relative directory path, so AI clients can inspect files without SSH.

Instructions

Read the full text content of a file on the cPanel server.

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": {
      "file": "<file>"
    },
    "name": "read_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNoRelative directory path (leave empty for root).
fileYesFile name to read (e.g., index.php, style.css).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. Saying 'full text content' usefully implies a complete, text-only read with no line ranges or partial offsets, but nothing is said about permissions, path resolution relative to the home directory, size or truncation limits on large files, or behavior when the file is missing or binary.

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?

A single front-loaded sentence with zero filler; the purpose leads immediately. It is efficient, though the terseness is part of why behavioral and usage gaps remain.

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?

For a simple two-parameter read tool with a fully documented schema and no output schema to explain, the description covers the essentials. However, with no annotations at all, an agent gets no signal about access limits, encoding, or failure modes for this read operation.

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%, with 'dir' and 'file' both documented in the schema including examples and the empty-string root default. The description adds no meaning beyond that, so the baseline of 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 plus resource: 'Read the full text content of a file.' The addition of 'on the cPanel server' scopes where it operates, and the wording naturally separates it from write_file, delete_item, and list_files. It stops short of naming a sibling explicitly, but the action is unambiguous.

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 only implied by the verb – an agent infers this is the tool for retrieving file contents rather than listing, moving, or editing them. There is no guidance on prerequisites (does the path need to exist? is listing required first via list_files?) and no mention of when not to use it, such as for binary files.

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