Skip to main content
Glama
Sign In
forge

forge

by SoulNassim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

workspace_list

Lists files and folders in a project workspace, including the root, using an optional path relative to the workspace root so coding agents can inspect project contents.

Instructions

List a workspace folder ("" = root).

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

Input Schema

NameRequiredDescriptionDefault
pathNoPath relative to the workspace root.
projectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.3.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about recursion depth, hidden files, ordering, pagination, size limits, or read permissions. The single useful disclosure is that the empty path resolves to the workspace root.

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?

One short sentence with the root convention front-loaded and no filler. It is efficiently written, though its brevity borders on under-specification given the absence of annotations.

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 annotations and no output schema, the description is the only source of behavioral information, and it supplies almost none. An agent cannot tell what a returned listing looks like, whether it recurses, or how the undocumented 'project' parameter scopes the call.

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 50%: the schema documents that 'path' is relative to the workspace root, and the description adds the non-obvious "" = root convention, which is genuine added meaning. The 'project' parameter has no description in either place, so half the surface remains opaque.

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

Purpose3/5

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

States a verb (List) and a resource (workspace folder), which is enough to know it enumerates folder contents. However, it is ambiguous whether it lists the folder entry itself or its children, and it does nothing to separate it from close siblings such as workspace_overview or open_glob.

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?

The only usage hint is that an empty string means the workspace root; there is no guidance on when to use this versus workspace_overview, open_glob, or workspace_read. An agent must infer the choice from sibling names alone.

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