Skip to main content
Glama

get_workspace_structure

Retrieves the directory tree of a workspace or specific project, helping you understand the layout before reading files.

Instructions

Get the directory tree of the workspace or a specific project. Useful for understanding the layout before reading files.

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

Input Schema

NameRequiredDescriptionDefault
project_nameNoShow structure for a specific project. Omit to see all projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden alone. "Get" implies a non-destructive read, and the phrase "directory tree" signals a hierarchical return shape, but depth limits, hidden-file handling, and output size are not addressed. For a read-only tool that is adequate, though thin on specifics.

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, both load-bearing: the first states what is returned and its scope, the second states when to reach for it. The purpose is front-loaded and there is no filler.

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?

A simple one-optional-parameter read tool with no output schema needs little more than scope plus motivation, and both are present. Only the return format details (tree depth, entry granularity) are left unstated, a minor gap for a tool of this complexity.

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 optional project_name parameter is fully documented in the schema, including the omit-to-see-all behavior. The description adds only the phrase "or a specific project," which restates rather than extends the schema, so the baseline 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?

The description gives a specific verb and resource: "Get the directory tree of the workspace or a specific project," and states both scopes (whole workspace vs. one project). It is clear on its own, but it never names a sibling such as list_project_files or list_studio_projects, so the agent must infer that a directory tree differs from a flat file listing.

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?

"Useful for understanding the layout before reading files" gives a concrete when-to-use condition tied to a follow-up action. It stops short of naming an alternative tool or stating when not to use it, so it lands at clear context without exclusions.

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