Skip to main content
Glama

get-issue

Retrieve detailed information about a specific issue from a project in Plane.so to access status, descriptions, and related data for project management.

Instructions

Get detailed information about a specific issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesID of the project containing the issue
issue_idYesID of the issue to retrieve

Implementation Reference

  • Handler for the 'get-issue' tool: validates project_id and issue_id arguments, calls Plane API to fetch the issue details, and returns the JSON response.
    case "get-issue": {
      if (
        !args ||
        typeof args.project_id !== "string" ||
        typeof args.issue_id !== "string"
      ) {
        throw new Error("Project ID and Issue ID are required");
      }
      const { project_id, issue_id } = args;
      const issue = await callPlaneAPI(
        `/projects/${project_id}/issues/${issue_id}/`,
        "GET"
      );
      return {
        content: [{ type: "text", text: JSON.stringify(issue, null, 2) }],
        isError: false,
      };
    }
  • Schema definition for the 'get-issue' tool, specifying required project_id and issue_id inputs.
    const GET_ISSUE_TOOL: Tool = {
      name: "get-issue",
      description: "Get detailed information about a specific issue",
      inputSchema: {
        type: "object",
        properties: {
          project_id: {
            type: "string",
            description: "ID of the project containing the issue",
          },
          issue_id: {
            type: "string",
            description: "ID of the issue to retrieve",
          },
        },
        required: ["project_id", "issue_id"],
      },
    };
  • src/index.ts:262-271 (registration)
    Registration of the 'get-issue' tool in the listTools handler response, including it in the available tools list.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        LIST_PROJECTS_TOOL,
        GET_PROJECT_TOOL,
        CREATE_ISSUE_TOOL,
        LIST_ISSUES_TOOL,
        GET_ISSUE_TOOL,
        UPDATE_ISSUE_TOOL,
      ],
    }));
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 the tool retrieves information, implying a read-only operation, but doesn't clarify if it requires authentication, has rate limits, returns specific data formats, or handles errors. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 efficiently conveys the core purpose without unnecessary words. It's front-loaded with the essential action ('Get detailed information'), making it easy for an agent to parse quickly. Every word earns its place, achieving optimal conciseness.

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 tool's complexity (a read operation with 2 required parameters) and the lack of annotations and output schema, the description is incomplete. It doesn't address behavioral aspects like authentication needs, error handling, or return value structure, which are critical for an agent to use the tool effectively. The description should provide more context to compensate for these gaps.

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 description adds no parameter-specific information beyond what the input schema provides. Since schema description coverage is 100% (both parameters are well-documented with descriptions like 'ID of the project containing the issue'), the baseline score is 3. The description doesn't compensate with additional context, such as explaining ID formats or relationships between parameters.

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 tool's purpose with a specific verb ('Get') and resource ('detailed information about a specific issue'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list-issues' or 'get-project', which would require mentioning it retrieves a single issue by ID rather than listing multiple issues or fetching project 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing project and issue IDs), contrast with 'list-issues' for multiple issues, or specify use cases like viewing issue details after listing. This leaves the agent to infer usage from the tool name and parameters alone.

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