Skip to main content
Glama

test

Read-only

Evaluate file predicates such as existence, type, and permissions. Returns structured JSON with boolean result and exit code for conditional logic in scripts.

Instructions

Evaluate file predicates (exists, is_file, is_dir, is_executable, is_symlink, is_readable, is_writable) and return structured JSON with the boolean result. Read-only, no side effects. Returns JSON indicating test result and exit code (0 for true, 1 for false). Use for conditional branching based on file properties in scripts. Not for detailed file inspection — use 'stat' for full metadata. See also 'stat', '['.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNoPath is a regular file.
pathYesPath to test.
emptyNoPath is an empty regular file.
existsNoPath exists. This is the default predicate.
symlinkNoPath is a symbolic link.
readableNoPath is readable.
writableNoPath is writable.
directoryNoPath is a directory.
exit_codeNoReturn exit code 1 when predicates do not match.
non_emptyNoPath is a non-empty regular file.
executableNoPath is executable.
Behavior5/5

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

States read-only and no side effects (aligns with annotations), and details return format (JSON with boolean and exit code).

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 sentences plus a brief see-also; front-loaded with purpose and behavior; every sentence adds value.

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?

Describes output format and usage context; slightly unclear if multiple predicates can be set, but adequate for a simple file test tool.

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 covers 100% of parameters with descriptions; description summarizes predicates but adds minimal extra meaning beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description specifies verb 'evaluate' and resource 'file predicates', lists predicates, and distinguishes from siblings (stat, '[').

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

Usage Guidelines5/5

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

Explicitly advises use for conditional branching, warns against detailed inspection, and suggests alternatives (stat, '[').

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/caseSHY/AI-CLI'

If you have feedback or need assistance with the MCP directory API, please join our Discord server