Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

get_issue

Retrieve detailed information about a specific project issue in Zoho Projects using the project ID and issue ID.

Instructions

Get details of a specific issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID
issue_idYesIssue ID

Implementation Reference

  • The handler function that executes the 'get_issue' tool by calling the Zoho API to retrieve specific issue details and returns a formatted text response.
    private async getIssue(projectId: string, issueId: string) {
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects/${projectId}/issues/${issueId}`
      );
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • Identical handler function for the 'get_issue' tool in the HTTP server variant.
    private async getIssue(projectId: string, issueId: string) {
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects/${projectId}/issues/${issueId}`
      );
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • src/index.ts:400-411 (registration)
    Registration of the 'get_issue' tool in the ListTools response, including name, description, and input schema.
    {
      name: "get_issue",
      description: "Get details of a specific issue",
      inputSchema: {
        type: "object",
        properties: {
          project_id: { type: "string", description: "Project ID" },
          issue_id: { type: "string", description: "Issue ID" },
        },
        required: ["project_id", "issue_id"],
      },
    },
  • Tool registration in the HTTP server variant's ListTools response.
    {
      name: "get_issue",
      description: "Get details of a specific issue",
      inputSchema: {
        type: "object",
        properties: {
          project_id: { type: "string", description: "Project ID" },
          issue_id: { type: "string", description: "Issue ID" },
        },
        required: ["project_id", "issue_id"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'gets details' but doesn't clarify if this is a read-only operation, what permissions are required, how errors are handled, or the format of returned details, leaving significant gaps in understanding its behavior.

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, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 moderate complexity (fetching specific data with two required parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what details are returned, error conditions, or behavioral traits, leaving the agent with insufficient context for reliable use.

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, clearly documenting both parameters ('project_id' and 'issue_id') as required strings. The description adds no additional semantic context beyond implying these are needed to fetch issue details, so it meets the baseline for adequate but unenriched parameter information.

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 ('details of a specific issue'), making it easy to understand what it does. However, it doesn't distinguish itself from sibling tools like 'get_project' or 'get_task' beyond the resource type, missing 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'list_issues' for browsing or 'search' for filtering, nor does it specify prerequisites such as needing an existing issue ID, leaving usage context unclear.

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/qpiai/zoho-projects-mcp'

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