Skip to main content
Glama

agentbay_project_get

Get project details: fetch brief, stats, and member list using project ID or slug.

Instructions

Get project details including brief, stats, and member list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID or slug

Implementation Reference

  • src/index.ts:219-235 (registration)
    Tool registration for 'agentbay_project_get' using server.tool() on the McpServer instance. Defines the tool name, description, input schema (projectId: z.string()), and the handler callback.
    // Tool 13: Project Get
    server.tool(
      'agentbay_project_get',
      'Get project details including brief, stats, and member list',
      { projectId: z.string().describe('Project ID or slug') },
      async ({ projectId }) => {
        const data = await apiGet(`/api/v1/projects/${projectId}`);
        if (data.error) return { content: [{ type: 'text' as const, text: `Error: ${data.error}` }] };
        let text = `# ${data.name}\n`;
        text += `ID: ${data.id} | Slug: ${data.slug} | Visibility: ${data.visibility}\n`;
        if (data.description) text += `\n${data.description}\n`;
        if (data.brief) text += `\n## Brief\n${data.brief}\n`;
        const c = data._count || {};
        text += `\n**Stats**: ${c.files || 0} files | ${c.tasks || 0} tasks | ${c.attempts || 0} attempts | ${c.knowledge || 0} knowledge | ${c.members || 0} members`;
        return { content: [{ type: 'text' as const, text }] };
      }
    );
  • Handler function for agentbay_project_get. Makes a GET request to /api/v1/projects/${projectId}, then formats the response into a markdown string with project name, ID, slug, visibility, description, brief, and stats (files, tasks, attempts, knowledge, members).
    async ({ projectId }) => {
      const data = await apiGet(`/api/v1/projects/${projectId}`);
      if (data.error) return { content: [{ type: 'text' as const, text: `Error: ${data.error}` }] };
      let text = `# ${data.name}\n`;
      text += `ID: ${data.id} | Slug: ${data.slug} | Visibility: ${data.visibility}\n`;
      if (data.description) text += `\n${data.description}\n`;
      if (data.brief) text += `\n## Brief\n${data.brief}\n`;
      const c = data._count || {};
      text += `\n**Stats**: ${c.files || 0} files | ${c.tasks || 0} tasks | ${c.attempts || 0} attempts | ${c.knowledge || 0} knowledge | ${c.members || 0} members`;
      return { content: [{ type: 'text' as const, text }] };
    }
  • Input schema for the tool: a required 'projectId' field of type z.string(), described as 'Project ID or slug'.
    { projectId: z.string().describe('Project ID or slug') },
  • Helper function apiGet used by the handler to make authenticated GET requests to the API base URL.
    async function apiGet(path: string) {
      const res = await fetch(`${API_BASE}${path}`, { headers: getHeaders() });
      return res.json();
    }
Behavior3/5

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

With no annotations, the description carries the burden. It states it retrieves details but does not disclose side effects (none expected), permissions, or error conditions. Adequate for a read operation but lacks depth.

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?

A single, front-loaded sentence with no extraneous information. Every word adds value, achieving maximum conciseness.

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?

For a simple retrieval tool with one parameter and no output schema, the description is nearly complete. It covers purpose and output content, though it omits potential error states or additional result details.

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?

The schema covers 100% of the parameter (projectId), already describing it as 'Project ID or slug'. The description adds output context (brief, stats, member list) but does not enhance parameter understanding beyond schema.

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?

The description clearly states the verb 'Get' and the resource 'project details', and it lists specific components (brief, stats, member list), effectively distinguishing it from sibling tools like agentbay_project_list.

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 this tool versus alternatives (e.g., agentbay_project_list). The context implies use for specific project details, but lacks direct exclusions or alternative references.

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