Zoho Projects MCP Server

Overview Schema Source Related Servers Discussions Admin

get_task

Retrieve specific task details from Zoho Projects by providing project and task IDs to access task information for project management.

Instructions

Get details of a specific task

Input Schema

TableJSON Schema

Name	Required	Description	Default
`project_id`	Yes	Project ID
`task_id`	Yes	Task ID

Implementation Reference

src/index.ts:720-727 (handler)

Core handler function for 'get_task' tool. Fetches task details via Zoho Projects API using makeRequest and returns JSON-formatted response.

private async getTask(projectId: string, taskId: string) {
  const data = await this.makeRequest(
    `/portal/${this.config.portalId}/projects/${projectId}/tasks/${taskId}`
  );
  return {
    content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
  };
}

src/index.ts:305-315 (schema)

Tool definition including name, description, and input schema (JSON Schema) for validation of parameters: project_id and task_id as required strings.

  name: "get_task",
  description: "Get details of a specific task",
  inputSchema: {
    type: "object",
    properties: {
      project_id: { type: "string", description: "Project ID" },
      task_id: { type: "string", description: "Task ID" },
    },
    required: ["project_id", "task_id"],
  },
},

src/index.ts:574-575 (registration)
Registration/dispatch in the CallToolRequestSchema handler switch statement, routing 'get_task' calls to the getTask method.
```
case "get_task":
  return await this.getTask(params.project_id, params.task_id);
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2025

TDQS

C2.9/5.0

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 disclosing behavioral traits. It only implies a read operation ('Get details') but omits information about authentication, response format, failure behavior, or whether the task must exist.

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 that front-loads the verb and avoids superfluous content. It is efficient but could include a brief note about required identifiers without losing conciseness.

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 tool's simplicity (two parameters, no nested objects), the description is minimally adequate, but it does not explain what 'details' entails or what the response looks like. The absence of an output schema makes this lack of return information more significant.

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?

Both parameters are already documented in the schema with descriptions ('Task ID', 'Project ID'), achieving 100% schema coverage. The description adds no additional meaning or context beyond what the schema provides, so the baseline of 3 is appropriate.

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 ('Get') and the resource ('details of a specific task'), making it easy to understand the tool's core purpose. It distinguishes itself from list_tasks by focusing on a single task, though it does not explicitly call out alternatives like get_task_by_prefix.

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 such as list_tasks or get_task_by_prefix. It leaves the agent to infer usage context from the name and schema, which is insufficient.

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