Skip to main content
Glama

get_project_note

Retrieve detailed information about a specific note in a project using its project ID and note ID.

Instructions

指定したプロジェクト内の特定のノートの詳細を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesプロジェクトID
noteIdYesノートID

Implementation Reference

  • index.js:549-560 (registration)
    The tool 'get_project_note' is registered in the ListToolsRequestSchema handler with its name, description, and input schema (projectId and noteId required).
    {
      name: 'get_project_note',
      description: '指定したプロジェクト内の特定のノートの詳細を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          projectId: { type: 'string', description: 'プロジェクトID' },
          noteId: { type: 'string', description: 'ノートID' },
        },
        required: ['projectId', 'noteId'],
      },
    },
  • The tool execution handler in CallToolRequestSchema that calls this.repsonaAPI.getProjectNote() with projectId and noteId arguments and returns the result as JSON text.
    case 'get_project_note':
      const projectNote = await this.repsonaAPI.getProjectNote(args.projectId, args.noteId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(projectNote, null, 2),
          },
        ],
      };
  • The RepsonaAPI helper method that makes a GET request to `/project/{projectId}/note/{noteId}` to fetch a specific note's details.
    async getProjectNote(projectId, noteId) {
      return this.makeRequest(`/project/${projectId}/note/${noteId}`);
    }
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It does not disclose whether the operation is read-only, what authentication is needed, or any side effects. The mere assertion 'get details' implies a read operation but lacks depth.

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 concise sentence with no wasted words. It effectively conveys the core purpose, though it is not in English (the likely language for AI agents).

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?

With no output schema, the description should explain what 'details' includes (e.g., title, content, metadata). It fails to set expectations for the return value, leaving the agent uncertain about the response format.

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 (projectId, noteId) having descriptions in the schema. The tool description adds no additional meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 ('get details') and the resource ('specific note within a specified project'). However, it does not distinguish from sibling tools like get_project_note_comments or get_project_note_history, which may cause confusion about which tool to use for full details.

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 such as get_project_note_children (to get child notes) or get_project_note_activity_log (to get activity logs). The description offers no context for selection.

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