custom-zoho-project-mcp-server

remove_portal_selection

Remove a specific portal/project pair from the current selection, automatically activating another remaining selection if the removed pair was active.

Instructions

Remove one portal/project pair from the selected set. If it was active, another remaining selection (if any) becomes active.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "portal_id": "<portal_id>",
      "project_id": "<project_id>"
    },
    "name": "remove_portal_selection"
  }
}

Input Schema

Name	Required	Description	Default
`portal_id`	Yes
`project_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 24, 2026

TDQS

A4.2/5.0

Behavior4/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 behavioral disclosure, and it does disclose a key non-obvious behavior: if the removed pair was active, another remaining selection becomes active. It does not mention failure modes or permissions, but for this simple state mutation the critical behavioral nuance is covered.

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 focused sentence with a conditional follow-up that adds essential behavior. Every word earns its place, and the main action is front-loaded.

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?

For a simple two-parameter tool with an output schema, the description is nearly complete: it states the operation, the object, and the active-selection fallback behavior. It does not explicitly state prerequisites such as 'the pair must already be selected,' but that is strongly implied by the phrase 'from the selected set.'

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 0%, so the description must compensate. It adds the useful semantic that portal_id and project_id together form a pair within the selected set, but it does not clarify where these IDs come from or any formatting constraints. The parameter names and titles are self-explanatory enough to make the description minimally viable.

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 uses a specific verb ('Remove') with a precise resource ('one portal/project pair from the selected set'), making the operation unambiguous. It also implicitly differentiates from siblings like reset_selection by emphasizing removal of a single pair rather than clearing the entire selection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context: use this when you need to remove one portal/project pair from the current selected set. It does not explicitly name alternatives or exclusions, such as 'for removing all, use reset_selection,' but the scope of the operation is clearly implied.

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

Deploy Server