Skip to main content
Glama

get_project_notes

Retrieve all notes from a specified project using its project ID.

Instructions

指定したプロジェクト内のノート一覧を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesプロジェクトID

Implementation Reference

  • Handler for the 'get_project_notes' tool: calls this.repsonaAPI.getProjectNotes(args.projectId) and returns the result as JSON stringified text.
    case 'get_project_notes':
      const projectNotes = await this.repsonaAPI.getProjectNotes(args.projectId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(projectNotes, null, 2),
          },
        ],
      };
  • Schema definition for 'get_project_notes' tool, defining the input schema with a required projectId string property.
      name: 'get_project_notes',
      description: '指定したプロジェクト内のノート一覧を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          projectId: { type: 'string', description: 'プロジェクトID' },
        },
        required: ['projectId'],
      },
    },
  • index.js:539-548 (registration)
    Tool 'get_project_notes' is registered in the ListToolsRequestSchema handler as part of the tools array.
      name: 'get_project_notes',
      description: '指定したプロジェクト内のノート一覧を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          projectId: { type: 'string', description: 'プロジェクトID' },
        },
        required: ['projectId'],
      },
    },
  • Helper method in RepsonaAPI class that makes the actual API request to GET /project/{projectId}/note to fetch project notes.
    async getProjectNotes(projectId) {
      return this.makeRequest(`/project/${projectId}/note`);
    }
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. However, it only states the basic purpose and does not disclose any behavioral traits such as pagination, ordering, scope (e.g., only accessible notes), or whether it includes archived/deleted notes. This lack of detail leaves the agent with incomplete information.

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, concise sentence that conveys the core purpose without any unnecessary words. It is well-structured and front-loaded.

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?

Given the tool's simplicity (one parameter, no output schema), the description is minimally adequate. However, it lacks details about the return format, ordering, or filtering capabilities, which would enhance completeness for an agent.

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 for the single parameter (projectId described as 'プロジェクトID'). The description does not add any additional meaning beyond what the schema 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.

Purpose5/5

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

The description clearly states it retrieves a list of notes within a specified project, using a specific verb ('取得') and resource ('ノート一覧'). It effectively distinguishes itself from siblings like 'get_project_note' which retrieves a single note.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for listing notes, but provides no explicit guidance on when to use this tool versus alternatives (e.g., get_project_note for a specific note, or create_project_note for adding notes). No when-not or alternative suggestions are given.

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