Skip to main content
Glama

List Projects

list_projects
Read-onlyIdempotent

Retrieve all MantisBT projects available to the current API user for managing bug tracking workflows.

Instructions

List all MantisBT projects accessible to the current API user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the `list_projects` tool that fetches projects from the MantisBT API and returns them as a JSON string.
    async () => {
      try {
        const result = await client.get<{ projects: MantisProject[] }>('projects');
        const projects = (result.projects ?? []).map(normalizeProject);
        return {
          content: [{ type: 'text', text: JSON.stringify(projects, null, 2) }],
        };
      } catch (error) {
        const msg = error instanceof Error ? error.message : String(error);
        return { content: [{ type: 'text', text: errorText(msg) }], isError: true };
      }
    }
  • Registration of the `list_projects` tool within the MCP server using `server.registerTool`.
    server.registerTool(
      'list_projects',
      {
        title: 'List Projects',
        description: 'List all MantisBT projects accessible to the current API user.',
        inputSchema: z.object({}),
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
        },
      },
      async () => {
        try {
          const result = await client.get<{ projects: MantisProject[] }>('projects');
          const projects = (result.projects ?? []).map(normalizeProject);
          return {
            content: [{ type: 'text', text: JSON.stringify(projects, null, 2) }],
          };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: 'text', text: errorText(msg) }], isError: true };
        }
      }
    );
Behavior3/5

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

Annotations already establish the operation is read-only, idempotent, and non-destructive. The description adds valuable authorization context ('accessible to the current API user'), but does not disclose pagination behavior, return format, or cache characteristics.

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 that front-loads the verb ('List'). There is no redundant or extraneous text; every word contributes to defining scope or authorization constraints.

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?

Given the tool's simplicity (zero parameters) and presence of annotations, the description is minimally sufficient. However, it misses the opportunity to clarify that this tool returns project identifiers/names typically required as prerequisites for sibling 'get_project_*' operations.

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 contains zero parameters. Per the baseline rules for parameter-less tools, this earns a 4. The description correctly implies no filtering parameters are accepted by stating it lists 'all' accessible projects.

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 clearly states the action ('List'), resource ('MantisBT projects'), and scope ('accessible to the current API user'). However, it does not explicitly distinguish from sibling tools like 'get_project_categories' or 'get_project_users', which likely require specific project IDs obtained from this list.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it explain the typical workflow (e.g., 'use this first to obtain project IDs for use with get_project_categories'). It merely states what the tool does in isolation.

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/dpesch/mantisbt-mcp-server'

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