Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

list_phases

Retrieve project phases and milestones from Zoho Projects to track progress and manage timelines effectively.

Instructions

List phases/milestones from a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID
pageNoPage number
per_pageNoItems per page

Implementation Reference

  • Core handler function implementing the list_phases tool: fetches project phases from Zoho API endpoint and returns formatted response.
    private async listPhases(
      projectId: string,
      page: number = 1,
      perPage: number = 10
    ) {
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects/${projectId}/phases?page=${page}&per_page=${perPage}`
      );
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • Duplicate handler function for list_phases tool in HTTP server variant: identical implementation fetching phases via Zoho API.
    private async listPhases(
      projectId: string,
      page: number = 1,
      perPage: number = 10
    ) {
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects/${projectId}/phases?page=${page}&per_page=${perPage}`
      );
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • Tool schema definition including input parameters for list_phases (project_id required, pagination optional).
    name: "list_phases",
    description: "List phases/milestones from a project",
    inputSchema: {
      type: "object",
      properties: {
        project_id: { type: "string", description: "Project ID" },
        page: { type: "number", description: "Page number", default: 1 },
        per_page: {
          type: "number",
          description: "Items per page",
          default: 10,
        },
      },
      required: ["project_id"],
    },
  • src/index.ts:594-595 (registration)
    Tool dispatch/registration in the CallToolRequestSchema handler switch statement.
    case "list_phases":
      return await this.listPhases(params.project_id, params.page, params.per_page);
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 the tool lists phases/milestones, implying a read-only operation, but doesn't mention pagination behavior, rate limits, authentication needs, or what happens if the project ID is invalid. For a tool with parameters like 'page' and 'per_page', 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, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse quickly. Every part of the sentence earns its place by conveying essential information.

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 complexity of a list operation with pagination parameters and no output schema, the description is insufficient. It doesn't explain the return format, error conditions, or behavioral aspects like pagination limits. With no annotations to supplement, this leaves critical gaps for an agent to understand how 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, clearly documenting all parameters ('project_id', 'page', 'per_page') with their types and defaults. The description adds no additional semantic context beyond what the schema provides, such as explaining what 'phases/milestones' entail or how pagination works in practice. This meets the baseline score since the schema does the heavy lifting.

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 action ('List') and resource ('phases/milestones from a project'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_projects' or 'list_tasks', which also list resources but for different entities, leaving some ambiguity about when to choose this specific tool over others.

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_projects' or 'list_tasks', nor does it specify prerequisites such as needing a valid project ID. This lack of context makes it harder for an agent to decide when this tool is appropriate.

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