Skip to main content
Glama
Sign In
zenhub-mcp

zenhub-mcp

by derekbar90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

zenhub_set_estimate

Assign a numerical estimate to a specific issue to track effort and prioritize work in ZenHub.

Instructions

Set an estimate for an issue

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": {
      "issue_id": "<issue_id>",
      "value": "<value>"
    },
    "name": "zenhub_set_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_idYesIssue ID
valueYesEstimate value

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.8

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits like idempotency, effect on existing estimates, or permission requirements. It does not provide any such information, leaving the agent to infer from the generic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with one sentence containing no wasted words. However, it could be slightly expanded to include more context without losing conciseness.

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 the simplicity of the tool (2 required params, no output schema), the description is insufficient. It does not explain what an estimate means in ZenHub, if there are constraints on the value, or what happens after setting (e.g., does it overwrite or append?).

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 input schema has 100% description coverage for both parameters. The description does not add additional meaning beyond what the schema provides, so it meets the baseline for schema-covered parameters.

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 action and resource: 'Set an estimate for an issue'. However, it does not differentiate from the sibling tool 'zenhub_set_multiple_estimates', which performs a similar action for multiple issues.

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 'zenhub_set_multiple_estimates'. The description lacks any context about prerequisites, typical use cases, or when not to use it.

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