Skip to main content
Glama

get_project_statuses

Retrieve all statuses for a project by providing its project ID. Use this to view or manage project states.

Instructions

指定したプロジェクトのステータス一覧を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesプロジェクトID

Implementation Reference

  • The tool handler that executes when 'get_project_statuses' is called. It calls the RepsonaAPI.getProjectStatuses method with the projectId argument and returns the result as formatted JSON.
    case 'get_project_statuses':
      const projectStatuses = await this.repsonaAPI.getProjectStatuses(args.projectId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(projectStatuses, null, 2),
          },
        ],
      };
  • The tool registration with its input schema. The tool requires a projectId (string) and returns the project statuses list.
    {
      name: 'get_project_statuses',
      description: '指定したプロジェクトのステータス一覧を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          projectId: { type: 'string', description: 'プロジェクトID' },
        },
        required: ['projectId'],
      },
    },
  • index.js:930-940 (registration)
    The tool is registered within the ListToolsRequestSchema handler, which lists all available tools for the MCP server.
    {
      name: 'get_project_statuses',
      description: '指定したプロジェクトのステータス一覧を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          projectId: { type: 'string', description: 'プロジェクトID' },
        },
        required: ['projectId'],
      },
    },
  • The RepsonaAPI helper method that makes the actual HTTP GET request to the Repsona API endpoint /project/{projectId}/status to retrieve project statuses.
    async getProjectStatuses(projectId) {
      return this.makeRequest(`/project/${projectId}/status`);
    }
Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It only states the function without mentioning read-only nature, permissions, or other side effects.

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 that conveys the purpose without waste. However, it could be slightly expanded for clarity.

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?

For a simple tool with one parameter and no output schema, the description provides the basic purpose. It lacks detail on what exactly constitutes a status or how the result is structured.

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% coverage with a clear parameter description. The description adds no additional meaning beyond the schema, which is acceptable per guidelines.

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 that the tool gets the list of statuses for a specified project. It is specific and distinct from sibling tools like get_project and get_project_activity, but lacks explicit differentiation.

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. There is no mention of context, prerequisites, or exclusions.

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