Skip to main content
Glama
Sign In
custom-zoho-project-mcp-server

custom-zoho-project-mcp-server

by harsh-simform
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_milestone_context

Retrieve complete milestone details and all linked tasks in one call to get a full overview of project progress.

Instructions

Full context for a milestone: its metadata plus every task under it.

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": {
      "milestone_id": "<milestone_id>"
    },
    "name": "get_milestone_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
milestone_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the return scope (all tasks under the milestone), but does not state whether the operation is read-only, whether large task counts are returned unbounded, or what the output structure looks like. The 'get' prefix implies read-only but this is not explicit.

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, front-loaded sentence with no filler. Every phrase earns its place, clearly conveying both the resource and the compositional scope.

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?

For a one-parameter retrieval tool, this is minimally adequate, but with no output schema and no annotations, the description does not disclose return shape, potential pagination, or scale warnings. The nature of 'full context' is hinted but not fully specified.

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

Parameters2/5

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

Schema description coverage is 0% and the description does not elaborate on milestone_id beyond 'milestone'. The parameter name is self-explanatory, but the description adds no format, source, or expected value details. With zero schema coverage, the description fails to compensate.

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 identifies the resource (milestone) and scope ('metadata plus every task under it'), which distinguishes it from sibling tools like get_task_context and get_project_context. It lacks an explicit verb like 'retrieve' or 'list', but the intent is unambiguous.

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

Usage Guidelines3/5

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

The description implies when to use this tool - when you need full context for a milestone including its tasks. However, it provides no explicit exclusions or comparisons to alternatives like get_task_context, leaving the agent to infer routing from the resource name.

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

Deploy Server

Other Tools