Skip to main content
Glama
nulab

Backlog MCP Server

get_project

Retrieve detailed information about a specific Backlog project using either its numeric ID or project key to access project data and settings.

Instructions

Returns information about a specific project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoThe numeric ID of the project (e.g., 12345)
projectKeyNoThe key of the project (e.g., 'PROJECT')

Implementation Reference

  • The handler function that resolves the project ID or key using resolveIdOrKey utility and retrieves the project details via the Backlog API.
    handler: async ({ projectId, projectKey }) => {
      const result = resolveIdOrKey(
        'project',
        { id: projectId, key: projectKey },
        t
      );
      if (!result.ok) {
        throw result.error;
      }
      return backlog.getProject(result.value);
    },
  • Input schema for the get_project tool using Zod, defining optional projectId (number) and projectKey (string) with descriptions.
    const getProjectSchema = buildToolSchema((t) => ({
      projectId: z
        .number()
        .optional()
        .describe(
          t(
            'TOOL_GET_PROJECT_PROJECT_ID',
            'The numeric ID of the project (e.g., 12345)'
          )
        ),
      projectKey: z
        .string()
        .optional()
        .describe(
          t(
            'TOOL_GET_PROJECT_PROJECT_KEY',
            "The key of the project (e.g., 'PROJECT')"
          )
        ),
    }));
  • The tool factory function that defines and exports the get_project tool, including name, description, input/output schemas, and handler.
    export const getProjectTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof getProjectSchema>,
      (typeof ProjectSchema)['shape']
    > => {
      return {
        name: 'get_project',
        description: t(
          'TOOL_GET_PROJECT_DESCRIPTION',
          'Returns information about a specific project'
        ),
        schema: z.object(getProjectSchema(t)),
        outputSchema: ProjectSchema,
        handler: async ({ projectId, projectKey }) => {
          const result = resolveIdOrKey(
            'project',
            { id: projectId, key: projectKey },
            t
          );
          if (!result.ok) {
            throw result.error;
          }
          return backlog.getProject(result.value);
        },
      };
    };
  • Instantiation and registration of the get_project tool factory within the central allTools function's 'project' toolset.
    getProjectTool(backlog, helper),
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Returns information' implies a read-only operation, but the description doesn't specify authentication requirements, rate limits, error conditions, or what happens if neither projectId nor projectKey is provided (both parameters are optional). For a tool with zero annotation coverage, this is insufficient behavioral context.

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 gets straight to the point: 'Returns information about a specific project'. There's no wasted language or unnecessary elaboration. It's appropriately sized for a simple retrieval tool.

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?

For a simple read operation with 2 optional parameters and 100% schema coverage, the description is minimally adequate. However, with no output schema and no annotations, the description doesn't explain what information is returned (project details, metadata, etc.) or address the behavioral gaps. It meets basic requirements but leaves important context unspecified.

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?

Schema description coverage is 100%, with both parameters clearly documented in the schema. The description adds no parameter information beyond what's already in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline score is 3 even with no param info in the description.

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 states the tool 'Returns information about a specific project', which is a clear verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'get_project_list' (which likely lists multiple projects) or 'get_space' (which might return project-related space information). The purpose is understandable but lacks sibling differentiation.

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. With sibling tools like 'get_project_list' (for listing projects) and 'get_space' (potentially for broader context), there's no indication of when this specific project retrieval tool is appropriate versus those alternatives. No prerequisites or exclusions are mentioned.

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/nulab/backlog-mcp-server'

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