Skip to main content
Glama

agentbay_project_list

Retrieve a list of all projects you are currently a member of within your MCP workspace.

Instructions

List projects you are a member of

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:203-217 (registration)
    The tool 'agentbay_project_list' is registered with the MCP server via server.tool() on line 203. It has no input schema (empty object {}) and its handler function calls apiGet('/api/v1/projects') to list projects the user is a member of.
    server.tool(
      'agentbay_project_list',
      'List projects you are a member of',
      {},
      async () => {
        const data = await apiGet('/api/v1/projects');
        if (data.error) return { content: [{ type: 'text' as const, text: `Error: ${data.error}` }] };
        const projects = data.projects || [];
        if (!projects.length) return { content: [{ type: 'text' as const, text: 'No projects found.' }] };
        const text = projects.map((p: any) =>
          `- **${p.name}** (${p.slug})\n  ID: ${p.id} | Files: ${p._count?.files || 0} | Tasks: ${p._count?.tasks || 0}`
        ).join('\n');
        return { content: [{ type: 'text' as const, text: `Your projects:\n\n${text}` }] };
      }
    );
  • The handler implementation for agentbay_project_list. It fetches projects from the API, checks for errors, formats the project list with name, slug, ID, file count and task count, and returns the result as text content.
    async () => {
      const data = await apiGet('/api/v1/projects');
      if (data.error) return { content: [{ type: 'text' as const, text: `Error: ${data.error}` }] };
      const projects = data.projects || [];
      if (!projects.length) return { content: [{ type: 'text' as const, text: 'No projects found.' }] };
      const text = projects.map((p: any) =>
        `- **${p.name}** (${p.slug})\n  ID: ${p.id} | Files: ${p._count?.files || 0} | Tasks: ${p._count?.tasks || 0}`
      ).join('\n');
      return { content: [{ type: 'text' as const, text: `Your projects:\n\n${text}` }] };
    }
  • The input schema for agentbay_project_list is an empty object ({}), meaning no parameters are required to call this tool.
    {},
  • The apiGet helper function used by the handler to make the GET request to the AgentBay API.
    async function apiGet(path: string) {
      const res = await fetch(`${API_BASE}${path}`, { headers: getHeaders() });
      return res.json();
    }
Behavior2/5

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

No annotations provided, and description only states scope ('member of') without behavioral details like authentication, pagination, or side effects. Minimal transparency.

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 sentence of 5 words, no wasted text, efficiently conveys the core purpose.

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?

Sufficient for a simple listing tool with no parameters, but lacks details on output format or prerequisites, leaving some gaps for an AI agent.

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?

With 0 parameters, description adds no param info; baseline 4 is appropriate as schema already fully covers the parameter space.

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 states 'List projects you are a member of', which is a specific verb (List) and resource (projects), clearly distinguishing from siblings like agentbay_project_get (single project).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use vs alternatives; usage is implied but lacks 'when not to use' or comparisons with sibling list tools.

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/thomasjumper/agentbay-mcp'

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