Skip to main content
Glama

workspace_list

Lists registered local workspaces so AI agents can identify available project contexts before routing skills or running workspace-specific operations.

Instructions

List registered local workspaces.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full load. "List" implies a non-destructive read and "registered local" narrows scope to locally registered workspaces, which is meaningful context. It says nothing about what a workspace entry contains, whether results are paginated, or where the data comes from, leaving real gaps for an unannotated tool.

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?

A single front-loaded sentence with zero filler and no hedging. It is efficient, though its brevity borders on under-specification for an agent that needs to know the return shape.

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?

The tool is trivial (zero params, no output schema, no nesting), so the description does not need much. However, with no output schema and no annotations, the agent gets no signal about what a returned workspace looks like or what "registered" means in practice.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. No parameter-level detail is missing because no parameters exist.

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?

"List registered local workspaces" pairs a specific verb (List) with a specific resource (registered local workspaces) and a scope qualifier (local, registered). It is clear what the tool returns and does not read like a restatement of the name alone. It stops short of explicitly contrasting with workspace_register, so it lands at 4 rather than 5.

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?

There is no when-to-use guidance, no exclusions, and no mention of the sibling workspace_register, which is the obvious complementary tool. The agent must infer that this is the discovery step before registration or health checks.

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