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);

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It indicates a read operation ('List') but does not mention that results are paginated or that it only applies to a single project. It does not describe any side effects or requirements beyond what is in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no wasted words. It is appropriately front-loaded but could arguably state a bit more without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple nature of the tool and full schema coverage, the description is minimally adequate but leaves gaps: it does not mention pagination, that project_id is required, or what the response contains. Since there is no output schema, this could be improved.

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 schema already provides descriptions for all three parameters (project_id, page, per_page). The description adds no additional parameter semantics beyond the phrase 'from a project', and does not elaborate on pagination or filtering behavior.

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

Purpose5/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 the resource (phases/milestones) and scopes it to a project, distinguishing it from sibling list tools like list_tasks or list_projects.

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 gives no explicit guidance on when to use this tool versus alternatives. It does not mention any exclusions or when not to use, leaving the agent to infer from the tool name and context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.