Skip to main content
Glama

list_projects

Retrieve all projects in your Vaiz workspace to view and manage current initiatives.

Instructions

List all projects in the current space

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool definition/schema for 'list_projects' — describes the tool name, description, and empty input schema (no parameters required). It's part of the hardcoded VAIZ_TOOLS array.
    {
      name: 'list_projects',
      description: 'List all projects in the current space',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Handler registration in proxy-server.ts. The 'list_projects' tool (like all tools) is made available via the tools/list handler which returns VAIZ_TOOLS merged with remote tools. The actual execution happens in the tools/call handler which proxies the request to the remote API.
    private registerHandlers(): void {
      const lowLevel = this.mcpServer.server;
    
      lowLevel.setRequestHandler(ListToolsRequestSchema, async () => {
        this.log('← tools/list');
        try {
          const result = (await this.proxyToRemote('tools/list')) as {
            tools?: Tool[];
          };
          const remoteTools = result?.tools ?? [];
          return { tools: mergeByName(VAIZ_TOOLS, remoteTools) };
        } catch {
          const cached = this.responseCache.get('tools/list') as {
            tools?: Tool[];
          } | undefined;
          return {
            tools: mergeByName(VAIZ_TOOLS, cached?.tools ?? []),
          };
        }
      });
    
      lowLevel.setRequestHandler(CallToolRequestSchema, async (request) => {
        this.log(`← tools/call ${request.params.name}`);
        const result = await this.proxyToRemote('tools/call', request.params);
        return result as { content: Array<{ type: string; text: string }> };
      });
    
      lowLevel.setRequestHandler(ListPromptsRequestSchema, async () => {
        this.log('← prompts/list');
        try {
          const result = (await this.proxyToRemote('prompts/list')) as {
            prompts?: Prompt[];
          };
          const remotePrompts = result?.prompts ?? [];
          return { prompts: mergeByName(VAIZ_PROMPTS, remotePrompts) };
        } catch {
          const cached = this.responseCache.get('prompts/list') as {
            prompts?: Prompt[];
          } | undefined;
          return {
            prompts: mergeByName(VAIZ_PROMPTS, cached?.prompts ?? []),
          };
        }
      });
    
      lowLevel.setRequestHandler(GetPromptRequestSchema, async (request) => {
        this.log(`← prompts/get ${request.params.name}`);
        const result = await this.proxyToRemote('prompts/get', request.params);
        return result as {
          description?: string;
          messages: Array<{
            role: 'user' | 'assistant';
            content: { type: string; text: string };
          }>;
        };
      });
    
      lowLevel.setRequestHandler(
        ListResourcesRequestSchema,
        async () => {
          this.log('← resources/list');
          try {
            const result = (await this.proxyToRemote('resources/list')) as {
              resources?: Resource[];
            };
            const remoteResources = result?.resources ?? [];
            return { resources: mergeByUri(VAIZ_RESOURCES, remoteResources) };
          } catch {
            const cached = this.responseCache.get('resources/list') as {
              resources?: Resource[];
            } | undefined;
            return {
              resources: mergeByUri(VAIZ_RESOURCES, cached?.resources ?? []),
            };
          }
        },
      );
    
      lowLevel.setRequestHandler(
        ReadResourceRequestSchema,
        async (request) => {
          this.log(`← resources/read ${request.params.uri}`);
          const result = await this.proxyToRemote(
            'resources/read',
            request.params,
          );
          return result as {
            contents: Array<{ uri: string; text?: string; mimeType?: string }>;
          };
        },
      );
    }
  • The call tool handler — when 'list_projects' is invoked by name, the request is forwarded via proxyToRemote to the remote Vaiz MCP API endpoint, which performs the actual project listing logic.
    lowLevel.setRequestHandler(CallToolRequestSchema, async (request) => {
      this.log(`← tools/call ${request.params.name}`);
      const result = await this.proxyToRemote('tools/call', request.params);
      return result as { content: Array<{ type: string; text: string }> };
    });
Behavior2/5

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

No annotations exist, and the description only states 'list' without disclosing read-only nature, authentication needs, or other behavioral traits.

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?

Single concise sentence with no redundancy, front-loaded with action and scope.

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?

Adequate for a parameterless list tool; however, missing details on return format or filtering, but minimal complexity keeps it complete enough.

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?

No parameters exist, so description has no param info to add; baseline of 4 applies as schema coverage is 100% and purpose already covers function.

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

Purpose5/5

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

Description clearly states verb 'List' and resource 'projects' with scope 'current space', distinguishing from sibling tools like list_boards or list_members.

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 on when to use vs alternatives such as list_boards or get_project; no exclusions or prerequisites provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vaizcom/vaiz-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server