Skip to main content
Glama

get-project

Retrieve detailed project information by ID to access project data and manage workflows through Plane's API.

Instructions

Get detailed information about a specific project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesID of the project to retrieve

Implementation Reference

  • Handler function for the 'get-project' tool. Validates input, calls Plane API to fetch project details by ID, and returns JSON response.
    case "get-project": {
      if (!args || typeof args.project_id !== "string") {
        throw new Error("Project ID is required");
      }
      const { project_id } = args;
      const project = await callPlaneAPI(`/projects/${project_id}/`, "GET");
      return {
        content: [{ type: "text", text: JSON.stringify(project, null, 2) }],
        isError: false,
      };
    }
  • Tool metadata definition including name, description, and input schema for 'get-project'.
    const GET_PROJECT_TOOL: Tool = {
      name: "get-project",
      description: "Get detailed information about a specific project",
      inputSchema: {
        type: "object",
        properties: {
          project_id: {
            type: "string",
            description: "ID of the project to retrieve",
          },
        },
        required: ["project_id"],
      },
    };
  • src/index.ts:262-271 (registration)
    Registration of the 'get-project' tool (as GET_PROJECT_TOOL) in the list of available tools returned by ListToolsRequestHandler.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        LIST_PROJECTS_TOOL,
        GET_PROJECT_TOOL,
        CREATE_ISSUE_TOOL,
        LIST_ISSUES_TOOL,
        GET_ISSUE_TOOL,
        UPDATE_ISSUE_TOOL,
      ],
    }));
  • Shared helper function callPlaneAPI used by the get-project handler to make authenticated API calls to Plane.
    async function callPlaneAPI(
      endpoint: string,
      method: string,
      body?: any
    ): Promise<any> {
      const baseUrl = `${PLANE_HOST}/api/v1/workspaces/${PLANE_WORKSPACE_SLUG}`;
      const url = `${baseUrl}${endpoint}`;
    
      const options: RequestInit = {
        method,
        headers: {
          "Content-Type": "application/json",
          "X-API-Key": PLANE_API_KEY as string,
        },
      };
    
      if (body && (method === "POST" || method === "PATCH")) {
        options.body = JSON.stringify(body);
      }
    
      try {
        const response = await fetch(url, options);
    
        if (!response.ok) {
          let errorText;
          try {
            errorText = await response.text();
          } catch (parseError) {
            errorText = "Unable to parse error response";
          }
          throw new Error(
            `Plane API error: ${response.status} ${response.statusText}\n${errorText}`
          );
        }
    
        // For DELETE requests that return 204 No Content
        if (response.status === 204) {
          return { success: true };
        }
    
        return await response.json();
      } catch (error) {
        throw new Error(
          `Error calling Plane API: ${
            error instanceof Error ? error.message : String(error)
          }`
        );
      }
    }
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. It states it 'Get[s] detailed information', which implies a read-only operation, but doesn't specify what 'detailed information' includes, whether it requires authentication, rate limits, error handling, or response format. This leaves significant gaps for a tool with no annotation coverage.

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, clear sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded and efficiently conveys the essential information, making it highly concise and well-structured.

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?

Given the lack of annotations and output schema, the description is insufficient for a tool that retrieves 'detailed information'. It doesn't explain what information is returned, potential errors, or behavioral traits, leaving the agent with incomplete context to use the tool effectively.

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, with the parameter 'project_id' clearly documented. The description adds no additional meaning beyond the schema, such as format examples or constraints, but since the schema is comprehensive, the baseline score of 3 is appropriate as it doesn't detract from the existing documentation.

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 verb ('Get') and resource ('detailed information about a specific project'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'list-projects', but the specificity of 'detailed information about a specific project' versus 'list-projects' implies a distinction between retrieving a single item versus multiple items.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list-projects' or 'get-issue'. It mentions 'specific project' which implies it's for single-project retrieval, but there's no explicit comparison or context about prerequisites, error conditions, or alternative tools.

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/kelvin6365/plane-mcp-server'

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