Skip to main content
Glama
Sign In
Txa_MCP

Txa_MCP

by TXAVLOG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

read_dir

Lists files in a directory with detailed information. Can access directories outside the project root when user explicitly approves.

Instructions

Liệt kê danh sách file trong thư mục với thông tin chi tiết.

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

Input Schema

NameRequiredDescriptionDefault
dirPathNoDirectory path.
allow_external_accessNoSet to true to allow reading directories outside the project root. User must explicitly approve this action.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.3

TDQS

C2.9/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 full responsibility. It mentions 'with detailed information' but does not specify what details are included, whether the listing is recursive, or how errors are handled. The schema hints at external access approval, but the description itself adds no behavioral context.

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?

The description is a single, front-loaded sentence that is concise and free of unnecessary words. It effectively communicates the core purpose without bloat.

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?

With no output schema or annotations, the description is insufficiently complete. The phrase 'thông tin chi tiết' (detailed information) leaves the return format ambiguous, and there is no mention of edge cases, recursion behavior, or the significance of the allow_external_access parameter.

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?

The input schema already documents both parameters (dirPath and allow_external_access) with clear descriptions, achieving 100% schema coverage. The tool description adds no parameter-specific semantics, so the baseline score of 3 is appropriate.

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 'Liệt kê' (list) and a clear resource 'thư mục' (directory), effectively stating the tool's function. It does not explicitly differentiate from sibling tools like list_repositories or find_large_files, but the directory focus is implicit and distinct enough.

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 guidance on when to use this tool versus alternatives such as read_file or find_large_files. The description only states the basic function without context, limitations, or exclusions.

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

Deploy Server

Other Tools