Skip to main content
Glama
papunoko

Redmine MCP Server for Cline

by papunoko

create_issue

Create new issues in Redmine projects to track tasks, bugs, or feature requests through the Cline VS Code extension.

Instructions

Create a new Redmine issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID
subjectYesIssue subject
descriptionYesIssue description

Implementation Reference

  • Main handler for CallToolRequestSchema that implements the logic for the 'create_issue' tool, including validation, API call to Redmine, and response formatting.
    this.server.setRequestHandler(CallToolRequestSchema, async (request) => {
      if (request.params.name !== 'create_issue') {
        throw new McpError(
          ErrorCode.MethodNotFound,
          `Unknown tool: ${request.params.name}`
        );
      }
    
      if (!isValidCreateIssueArgs(request.params.arguments)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Invalid create_issue arguments'
        );
      }
    
      const { project_id, subject, description } = request.params.arguments;
    
      try {
        const issue = await new Promise((resolve, reject) => {
            redmine.create_issue({
            project_id: project_id,
            subject: subject,
            description: description,
          }, (err, data) => {
            if (err) {
              reject(err);
            } else {
              resolve(data);
            }
          });
        });
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(issue),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Redmine API error: ${error}`,
            },
          ],
          isError: true,
        };
      }
    });
  • Input schema definition for the create_issue tool, specifying required parameters and types.
    inputSchema: {
      type: 'object',
      properties: {
        project_id: {
          type: 'string',
          description: 'Project ID',
        },
        subject: {
          type: 'string',
          description: 'Issue subject',
        },
        description: {
          type: 'string',
          description: 'Issue description',
        },
      },
      required: ['project_id', 'subject', 'description'],
    },
  • server.js:122-147 (registration)
    Registration of the create_issue tool in the ListToolsRequestSchema response, including name, description, and schema.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        {
          name: 'create_issue',
          description: 'Create a new Redmine issue',
          inputSchema: {
            type: 'object',
            properties: {
              project_id: {
                type: 'string',
                description: 'Project ID',
              },
              subject: {
                type: 'string',
                description: 'Issue subject',
              },
              description: {
                type: 'string',
                description: 'Issue description',
              },
            },
            required: ['project_id', 'subject', 'description'],
          },
        },
      ],
    }));
  • Helper function used to validate the arguments passed to the create_issue tool.
    const isValidCreateIssueArgs = (
      args
    ) => typeof args === 'object' && args !== null && typeof args.project_id === 'string' && typeof args.subject === 'string' && typeof args.description === 'string';
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 states this is a creation operation but doesn't mention permissions required, whether it's idempotent, error handling, or what happens on success (e.g., returns an issue ID). For a mutation tool with zero annotation coverage, this leaves critical behavioral aspects unspecified.

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 with no wasted words. It's appropriately sized for a simple creation tool and front-loads the essential information, making it easy to parse 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 this is a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what the tool returns, error conditions, or behavioral nuances. The agent lacks critical information needed to use this tool effectively in real scenarios.

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%, so the input schema already documents all three parameters (project_id, subject, description) with basic descriptions. The tool description adds no additional parameter context beyond what's in the schema, resulting in the baseline score for high schema coverage.

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 ('Create a new') and resource ('Redmine issue'), making the purpose immediately understandable. However, it doesn't differentiate from siblings (though none exist) or specify what constitutes a 'Redmine issue' beyond the basic concept, which prevents a perfect score.

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, prerequisites, or contextual constraints. The description merely restates the tool's function without offering any usage context, which is a significant gap for effective agent decision-making.

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/papunoko/Redmine-MCP'

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