Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

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
NameRequiredDescriptionDefault
project_idYesProject ID
task_idYesTask ID

Implementation Reference

  • 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) }],
      };
    }
  • 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);
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it 'gets details' without disclosing behavioral traits like read-only nature, error handling, authentication needs, or rate limits. It's minimal and lacks necessary context for safe use.

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 zero waste. It's appropriately sized and front-loaded, making it easy to parse quickly without unnecessary elaboration.

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 no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what 'details' are returned, error conditions, or usage context, leaving significant gaps for an AI agent to understand the tool fully.

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?

Schema description coverage is 100%, so the schema already documents both parameters ('project_id' and 'task_id'). The description doesn't add any meaning beyond what the schema provides, such as explaining relationships between parameters. Baseline 3 is appropriate as the schema does the heavy lifting.

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 task' clearly states the verb ('Get') and resource ('task'), but it's vague about what 'details' include and doesn't distinguish from sibling tools like 'get_issue' or 'get_project'. It's functional but lacks specificity about scope or 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?

No guidance is provided on when to use this tool versus alternatives like 'list_tasks' or 'search'. The description implies it's for retrieving a single task, but there's no explicit context, prerequisites, or exclusions mentioned.

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