Skip to main content
Glama
fleagne

Backlog MCP Server

by fleagne

backlog_get_project

Retrieve project details using the Backlog API by specifying a project ID or key. Facilitates project management within the Backlog MCP Server.

Instructions

Performs an project get using the Backlog Project get API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdOrKeyYesProject ID or Project Key

Implementation Reference

  • The main handler function 'handleGetProject' for the 'backlog_get_project' tool. It parses input arguments against ProjectParamsSchema, fetches project details via projectService.getProject, formats the response, and handles errors.
    const handleGetProject: ToolHandler = async (args) => {
    	try {
    		try {
    			const validatedParams = ProjectParamsSchema.parse(args);
    
    			const text = await projectService.getProject(validatedParams);
    
    			return {
    				content: [
    					{
    						type: "text",
    						text: `Project details for ${validatedParams.projectIdOrKey}:\n${text}`,
    					},
    				],
    				isError: false,
    			};
    		} catch (validationError) {
    			throw new ValidationError(
    				`Invalid parameters: ${validationError instanceof Error ? validationError.message : String(validationError)}`,
    			);
    		}
    	} catch (error) {
    		return {
    			content: [
    				{
    					type: "text",
    					text: `Error: ${formatError(error)}`,
    				},
    			],
    			isError: true,
    		};
    	}
    };
  • Maps the tool name 'backlog_get_project' to its handler 'handleGetProject' in the central toolHandlers registry.
    export const toolHandlers: Record<ToolName, ToolHandler> = {
    	backlog_get_projects: handleGetProjects,
    	backlog_get_project: handleGetProject,
    	backlog_get_issues: handleGetIssues,
    	backlog_get_issue: handleGetIssue,
    	backlog_add_issue: handleAddIssue,
    	backlog_update_issue: handleUpdateIssue,
    	backlog_delete_issue: handleDeleteIssue,
    	backlog_get_wikis: handleGetWikis,
    	backlog_get_wiki: handleGetWiki,
    	backlog_add_wiki: handleAddWiki,
    	backlog_update_wiki: handleUpdateWiki,
    	backlog_delete_wiki: handleDeleteWiki,
    };
  • Zod schema defining the input parameters for the 'backlog_get_project' tool: requires 'projectIdOrKey'.
    export const ProjectParamsSchema = z.object({
    	projectIdOrKey: z.string().describe("Project ID or Project Key"),
    });
  • Defines the MCP Tool object for 'backlog_get_project' with description and input schema (converted from Zod).
    export const PROJECT_TOOL: Tool = createTool(
    	"backlog_get_project",
    	"Performs an project get using the Backlog Project get API.",
    	ProjectParamsSchema,
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool uses an API to 'get' a project, implying a read operation, but does not detail permissions, rate limits, error handling, or response format. This is inadequate for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words, making it front-loaded and easy to parse. However, it could be more structured by explicitly stating the tool's purpose upfront, but it remains appropriately sized for its content.

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 no annotations and no output schema, the description is incomplete. It lacks details on what the tool returns (e.g., project details), behavioral traits like authentication needs, and how it differs from siblings, making it insufficient for effective agent use.

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 input schema has 100% description coverage, documenting the 'projectIdOrKey' parameter as 'Project ID or Project Key.' The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline of 3 where the schema does the heavy lifting.

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 'Performs an project get using the Backlog Project get API,' which clarifies it retrieves project data but is vague about what 'get' entails (e.g., fetching details vs. listing). It distinguishes from siblings like 'backlog_get_projects' (plural) by implying a single project, but lacks specificity on the resource scope or verb nuance.

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. It does not mention prerequisites, exclusions, or comparisons to siblings like 'backlog_get_projects' for listing multiple projects or 'backlog_get_issue' for issue-related data, leaving usage context unclear.

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

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