Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

get_portal

Retrieve portal details by ID from Zoho Projects to access project management information and settings.

Instructions

Get details of a specific portal

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portal_idYesPortal ID

Implementation Reference

  • Core implementation of the get_portal tool handler. Fetches portal details from Zoho API endpoint `/portal/${portalId}` via makeRequest and formats response as MCP content block.
    private async getPortal(portalId: string) {
      const data = await this.makeRequest(`/portal/${portalId}`);
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • Core implementation of the get_portal tool handler. Fetches portal details from Zoho API endpoint `/portal/${portalId}` via makeRequest and formats response as MCP content block.
    private async getPortal(portalId: string) {
      const data = await this.makeRequest(`/portal/${portalId}`);
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • Tool registration entry for get_portal, including name, description, and input schema defining required 'portal_id' parameter.
      name: "get_portal",
      description: "Get details of a specific portal",
      inputSchema: {
        type: "object",
        properties: {
          portal_id: { type: "string", description: "Portal ID" },
        },
        required: ["portal_id"],
      },
    },
  • src/index.ts:189-198 (registration)
    Tool registration entry for get_portal, including name, description, and input schema defining required 'portal_id' parameter.
      name: "get_portal",
      description: "Get details of a specific portal",
      inputSchema: {
        type: "object",
        properties: {
          portal_id: { type: "string", description: "Portal ID" },
        },
        required: ["portal_id"],
      },
    },
  • Input schema for get_portal tool requiring a string portal_id.
    inputSchema: {
      type: "object",
      properties: {
        portal_id: { type: "string", description: "Portal ID" },
      },
      required: ["portal_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 for behavioral disclosure. It states this is a read operation ('Get details'), but doesn't mention permissions required, rate limits, error conditions, or what format/details are returned. For a tool with zero annotation coverage, this is insufficient.

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 wasted words. It's appropriately sized for a simple retrieval tool and gets straight to the point 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 and no output schema, the description should do more to explain what 'details' are returned, error handling, or authentication requirements. For a tool that presumably returns structured portal data, the description is too minimal to be complete.

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 description doesn't add any parameter information beyond what's already in the schema (which has 100% coverage). The schema fully documents the single 'portal_id' parameter, so the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't need to given complete schema coverage.

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 verb ('Get') and resource ('details of a specific portal'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'list_portals' which presumably lists multiple portals, leaving some ambiguity about when to use one versus the other.

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 like 'list_portals' or other get_* tools. It doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone.

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