Skip to main content
Glama
TrialRun MCP

TrialRun MCP

by kostadindev

List workspace files

list_files

Lists files the AI is allowed to see on the assessment desktop, hides blocked files, and can filter results by folder.

Instructions

List the files on the Fernvale Kitchens Ltd assessment desktop that the AI is allowed to see. Files the student has blocked are hidden.

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

Input Schema

NameRequiredDescriptionDefault
folderNoRestrict to one folder

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the access-filtering behavior (student-blocked files are hidden), which the agent could not infer from the schema, but it omits ordering, result size, whether subfolders are included, and any permission model beyond the visibility rule.

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?

Two short sentences, with the core scope front-loaded and the visibility caveat following. The second sentence largely restates the first in concrete terms, which adds clarity rather than waste, though it is mildly redundant.

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 one-parameter list tool this is close to sufficient, but with no output schema the description should indicate what the listing yields (names, paths, folders, sizes) so the agent knows how to use the result. That gap plus the unstated default for the folder filter keeps it at adequate rather than complete.

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 coverage is 100% and the single enum parameter is documented as "Restrict to one folder," so the schema already does the work. The description adds nothing about the folder filter, such as its default when omitted (all folders), 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 and resource ("List the files") plus the scope (the assessment desktop, limited to what the AI is allowed to see), so the agent knows this is a discovery/enumeration call rather than a content read like read_file. It does not explicitly name a sibling to contrast with, keeping it just short of a 5.

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?

The phrase "that the AI is allowed to see" implies this is the entry point for discovering what is available before reading files, but there is no explicit when-to-use, no named alternative (e.g. read_file), and no stated conditions or exclusions.

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