Skip to main content
Glama
Sign In
Alcove

Alcove

Official
by OctopusGarage
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

alcove_project_list

List globally defined project aliases, with optional filter by workspace or home directory.

Instructions

List global project aliases.

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

Input Schema

NameRequiredDescriptionDefault
homeNo
workspaceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description fails to disclose behavioral details like read-only status, authentication needs, or the effect of parameter values. The description only states the action, omitting critical context about side effects, permissions, or response behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short (one sentence) and front-loaded with the purpose, but it sacrifices necessary detail. While concise, it lacks structure that would convey parameter usage or context, making it minimally adequate.

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?

Given the availability of an output schema (unspecified content) and the complexity of list operations, the description is incomplete. It fails to mention filtering capabilities via the two parameters or clarify the scope of 'global project aliases,' leaving gaps for an AI agent.

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

Parameters1/5

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

The input schema has two parameters (home, workspace) with 0% description coverage, and the description does not explain their meaning or default behavior. The description adds no semantic value beyond the schema, leaving the agent to guess how these parameters affect the list output.

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 'List global project aliases' clearly states the verb (list) and resource (global project aliases), distinguishing it from siblings like alcove_project_get (single) and alcove_project_find (search). However, it does not clarify what 'global' means in this context, leaving some ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives such as alcove_project_find or alcove_project_get. The optional parameters home and workspace are not explained, leaving the agent uncertain about their purpose and when to include them.

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