Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

get_project

Retrieve specific project details from Zoho Projects by providing the project ID to access information for management and tracking.

Instructions

Get details of a specific project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID

Implementation Reference

  • Handler function that executes the get_project tool: makes API request to Zoho for project details and returns JSON-formatted response.
    private async getProject(projectId: string) {
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects/${projectId}`
      );
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • Input schema definition for the get_project tool, specifying project_id as required string.
    inputSchema: {
      type: "object",
      properties: {
        project_id: { type: "string", description: "Project ID" },
      },
      required: ["project_id"],
    },
  • src/index.ts:216-226 (registration)
    Tool registration in the list of tools returned by ListToolsRequestHandler, defining name, description, and schema.
    {
      name: "get_project",
      description: "Get details of a specific project",
      inputSchema: {
        type: "object",
        properties: {
          project_id: { type: "string", description: "Project ID" },
        },
        required: ["project_id"],
      },
    },
  • Identical handler function in the HTTP server implementation.
    private async getProject(projectId: string) {
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects/${projectId}`
      );
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • Tool registration in the HTTP server version.
    {
      name: "get_project",
      description: "Get details of a specific project",
      inputSchema: {
        type: "object",
        properties: {
          project_id: { type: "string", description: "Project ID" },
        },
        required: ["project_id"],
      },
    },
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 'Get details' but does not specify if this is a read-only operation, what permissions are required, how errors are handled, or the format of returned data. For a tool with zero annotation coverage, this leaves critical behavioral traits unaddressed.

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 with no wasted words. It is front-loaded and directly states the tool's purpose without unnecessary elaboration. Every part of the description earns its place, 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 incomplete for a tool that likely returns complex project data. It does not explain what 'details' include, error conditions, or response format, leaving gaps in context. For a read operation with no structured output, more completeness is needed.

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 'project_id' clearly documented. The description adds no additional meaning beyond the schema, such as examples or constraints on the ID format. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, but no extra value is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get details of a specific project' clearly states the verb ('Get') and resource ('project'), making the purpose understandable. However, it lacks specificity about what 'details' include and does not differentiate from sibling tools like 'list_projects' or 'get_task', which reduces clarity. It avoids tautology but remains vague.

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 does not mention prerequisites, such as needing a project ID, or compare it to siblings like 'list_projects' for browsing or 'get_task' for related resources. Without any usage context, the agent must infer from tool names 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/qpiai/zoho-projects-mcp'

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