Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

list_portals

Retrieve all available Zoho Projects portals to access and manage your project workspaces through the MCP server.

Instructions

Retrieve all Zoho Projects portals

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function for the 'list_portals' tool. Makes an API request to Zoho's /portals endpoint and returns the response as formatted JSON text content.
    private async listPortals() {
      const data = await this.makeRequest("/portals");
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • Identical core handler function for the 'list_portals' tool in the HTTP server variant.
    private async listPortals() {
      const data = await this.makeRequest("/portals");
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • src/index.ts:181-187 (registration)
    Tool registration entry in the listTools handler, including name, description, and schema.
      name: "list_portals",
      description: "Retrieve all Zoho Projects portals",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema for the 'list_portals' tool, which requires no parameters.
    inputSchema: {
      type: "object",
      properties: {},
    },
  • src/index.ts:554-558 (registration)
    Dispatch/registration in the callTool request handler switch statement.
    case "list_portals":
      return await this.listPortals();
    case "get_portal":
      return await this.getPortal(params.portal_id);

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It indicates a read-only operation ('Retrieve all'), but does not disclose potential pagination, response size, or authentication requirements. For a simple list-all with no parameters, this is adequate but not rich.

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, compact sentence with no redundant words. It front-loads the action and resource, achieving maximum conciseness.

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

Completeness4/5

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

Given the tool's simplicity (no params, no output schema), the description sufficiently communicates the action and scope. However, it does not describe the return structure or any pagination behavior, which would be a minor gap for richer context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and the schema is empty (100% coverage by default). The description implies no filtering is needed ('all portals'), aligning with the schema. Baseline for 0 params is 4, and the description adds slight semantic confirmation.

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 verb 'Retrieve' and the resource 'all Zoho Projects portals', making it unambiguous. This distinguishes it from siblings like get_portal (single portal) and list_projects (different resource).

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 get_portal or list_projects. There are no explicit alternatives or exclusions, leaving the agent to infer usage context.

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