Skip to main content
Glama

get_projects

Retrieve active project lists from Mantis Bug Tracker to streamline project tracking and management within the Mantis MCP Server environment.

Instructions

獲取 Mantis 專案列表

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server.ts:187-197 (registration)
    Registration of the 'get_projects' MCP tool, including name, description, empty input schema, and inline handler function.
    server.tool(
      "get_projects",
      "獲取 Mantis 專案列表",
      {},
      async () => {
        return withMantisConfigured("get_projects", async () => {
          const projects = await mantisApi.getProjects();
          return JSON.stringify(projects, null, 2);
        });
      }
    );
  • Core handler logic in MantisApi class that fetches the list of projects from the Mantis API endpoint '/projects' using cached request.
    async getProjects(): Promise<Project[]> {
      log.info('獲取項目列表');
      
      const cacheKey = 'projects';
      
      return this.cachedRequest<Project[]>(cacheKey, () => {
        return this.api.get('/projects');
      });
    }
  • TypeScript interface defining the Project type returned by getProjects.
    export interface Project {
      id: number;
      name: string;
      description: string;
      enabled: boolean;
      status: {
        id: number;
        name: string;
      };
    }
  • Wrapper handler in server.tool that handles MCP response formatting, error handling via withMantisConfigured, and JSON serialization.
    async () => {
      return withMantisConfigured("get_projects", async () => {
        const projects = await mantisApi.getProjects();
        return JSON.stringify(projects, null, 2);
      });
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('獲取' - get) without detailing traits such as whether it's read-only, if it requires authentication, rate limits, pagination, or error handling. This leaves significant gaps in understanding how the tool behaves beyond its basic purpose.

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?

The description is a single, efficient sentence in Chinese that directly states the tool's purpose without any unnecessary words. It is front-loaded and appropriately sized for a simple list operation, making it easy to parse and understand quickly.

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 tool's simplicity (0 parameters, no output schema, no annotations), the description is minimal but lacks completeness. It doesn't address behavioral aspects like read-only nature, potential authentication needs, or output format, which are important even for basic tools. Without annotations or output schema, more context in the description would be beneficial.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, and it correctly implies no inputs are required for listing projects, aligning with the schema. This meets the baseline for tools with no parameters.

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

Purpose3/5

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

The description '獲取 Mantis 專案列表' (Get Mantis project list) clearly states the verb ('獲取' - get) and resource ('Mantis 專案列表' - Mantis project list), making the purpose understandable. However, it doesn't differentiate from sibling tools like get_issues or get_users, which also retrieve lists of different resources, leaving room for ambiguity about when to use this specific tool.

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. The description doesn't mention context, prerequisites, or exclusions, and it fails to distinguish it from sibling tools like get_issues or get_users, which could lead to confusion about selecting the right tool for listing projects versus other entities.

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

Related 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/kfnzero/mantis-mcp-server'

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