Skip to main content
Glama

get_project

Retrieve detailed information and metadata about a project using its ID.

Instructions

指定したプロジェクトの詳細情報を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesプロジェクトID

Implementation Reference

  • Handler for the 'get_project' tool: calls this.repsonaAPI.getProject(args.projectId) and returns JSON response. This is the main execution logic invoked when the tool is called.
    case 'get_project':
      const project = await this.repsonaAPI.getProject(args.projectId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(project, null, 2),
          },
        ],
      };
  • Input schema registration for the 'get_project' tool, defining projectId as required string parameter.
    {
      name: 'get_project',
      description: '指定したプロジェクトの詳細情報を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          projectId: { type: 'string', description: 'プロジェクトID' },
        },
        required: ['projectId'],
      },
    },
  • index.js:869-879 (registration)
    Registration of 'get_project' tool in ListToolsRequestSchema handler, listing tool name, description, and inputSchema.
    {
      name: 'get_project',
      description: '指定したプロジェクトの詳細情報を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          projectId: { type: 'string', description: 'プロジェクトID' },
        },
        required: ['projectId'],
      },
    },
  • RepsonaAPI.getProject() helper method that makes the actual API request to '/project/{projectId}' endpoint.
    async getProject(projectId) {
      return this.makeRequest(`/project/${projectId}`);
    }
Behavior3/5

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

No annotations provided, so the description carries full burden. It states the safe read operation without extra behavioral context. Adequate but not enriched.

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 wasted words. Front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter retrieval tool, the description is complete enough. Minor gap: no mention of return details, but not critical given no output schema.

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 has 100% coverage for the single parameter. The description adds no extra meaning beyond the schema, meeting the baseline.

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 action ('gets'), the resource ('project'), and the scope ('detailed info'). It distinguishes itself from siblings like get_projects (list) and update_project (modify).

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?

No explicit guidance on when to use or alternatives, but the purpose is straightforward and implied usage is obvious for a simple retrieval tool.

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