Skip to main content
Glama
Sign In
AgentsID Guard

AgentsID Guard

Official
by AgentsID-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

file_list

List files in a directory with size and type information, gated by file.list permission.

Instructions

List files in a directory with size and type info. Requires file.list permission.

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

Input Schema

NameRequiredDescriptionDefault
pathNoDirectory path (default: working directory)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the disclosure burden. It discloses the return content (size and type) and the required permission (file.list), which are useful behavioral traits. However, it does not mention recursion behavior, hidden files, or sorting, which are common list-operation variants.

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 two short sentences, immediately states the core action, and includes essential permission info without any filler. Every sentence earns its place.

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?

The tool is simple with one optional parameter and no output schema. The description adequately covers what it does and what it returns, though it could mention depth/hidden-file behavior. Given the lack of annotations, it is reasonably complete but not exhaustive.

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 schema already fully describes the single parameter 'path' with 100% coverage, including its default. The description adds no new parameter-level semantics; it only reiterates the general purpose, so the baseline of 3 applies.

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?

The description uses a specific verb ('List') and resource ('files in a directory') and adds output details ('with size and type info'), making it clear what the tool does and distinguishing it from sibling tools like file_read (contents) and file_info (metadata).

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 provides clear context: this tool lists files in a directory and requires the file.list permission. However, it does not explicitly contrast with alternatives like file_info or file_read, nor does it specify when not to use it, so it stops short of full usage guidance.

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