Skip to main content
Glama

create_project_note_comment

Post a comment to a specific note in a Repsona project. Use project ID and note ID to add or reply to note comments.

Instructions

指定したプロジェクト内のノートにコメントを投稿します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesプロジェクトID
noteIdYesノートID
commentYesコメント内容
parentNo返信先コメントID

Implementation Reference

  • index.js:629-642 (registration)
    Tool registration in ListToolsRequestSchema handler - defines the tool name, description, and input schema for create_project_note_comment
    {
      name: 'create_project_note_comment',
      description: '指定したプロジェクト内のノートにコメントを投稿します',
      inputSchema: {
        type: 'object',
        properties: {
          projectId: { type: 'string', description: 'プロジェクトID' },
          noteId: { type: 'string', description: 'ノートID' },
          comment: { type: 'string', description: 'コメント内容' },
          parent: { type: 'number', description: '返信先コメントID' },
        },
        required: ['projectId', 'noteId', 'comment'],
      },
    },
  • Handler logic in CallToolRequestSchema switch-case - extracts args and calls the API method createProjectNoteComment
    case 'create_project_note_comment':
      const { projectId: commentProjectId, noteId: commentNoteId, ...commentData } = args;
      const newNoteComment = await this.repsonaAPI.createProjectNoteComment(commentProjectId, commentNoteId, commentData);
      return {
        content: [
          {
            type: 'text',
            text: `プロジェクト内のノートにコメントが投稿されました: ${JSON.stringify(newNoteComment, null, 2)}`,
          },
        ],
      };
  • RepsonaAPI helper method that makes the actual HTTP POST request to the Repsona API to create a note comment
    async createProjectNoteComment(projectId, noteId, comment) {
      return this.makeRequest(`/project/${projectId}/note/${noteId}/note_comment`, 'POST', comment);
    }
Behavior3/5

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

With no annotations, the description conveys creation but lacks details on side effects (e.g., whether parent must exist, if note must exist, or any error conditions). Adequate but minimal.

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?

Single sentence, no unnecessary words. Front-loaded with the core action.

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?

No output schema and no mention of return value. Missing information about authentication or what happens on success/failure. Incomplete for a creation tool.

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 coverage is 100% with descriptions for all parameters. The description adds no additional semantics beyond schema, so baseline 3.

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

Purpose5/5

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

The description clearly states the verb 'post' and the resource 'comment to a note in a project'. It is specific and distinguishes from sibling tools like create_task_comment.

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 on when to use this tool vs alternatives (e.g., updating or deleting a comment), nor any prerequisites like project/note existence or permissions.

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/bellx2/repsona-mcp-server'

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