Skip to main content
Glama
Sign In
zenhub-mcp

zenhub-mcp

by derekbar90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

zenhub_get_organization_workspaces

Retrieve all workspaces belonging to a ZenHub organization, with optional filtering by name and pagination control.

Instructions

Get all workspaces within a specific ZenHub organization

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zenhub_get_organization_workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional search query to filter organizations
firstNoNumber of organizations to return (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.8

TDQS

C2.4/5.0
Behavior2/5

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

No annotations provided; description only states a generic operation. It fails to disclose authentication requirements, rate limits, or what 'get all workspaces' entails. Additionally, the parameter descriptions contradict the tool's purpose, reducing transparency.

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?

Single sentence is concise, but lacks any structural elements like bullet points or sections. It is appropriate for a simple tool but could be more informative.

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 existence of sibling tools and no output schema, more context is needed about how this tool differs from zenhub_get_user_workspaces and what the return format is. The parameter confusion makes the definition incomplete.

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 descriptions exist for both parameters but are misleading: 'query' and 'first' are described in terms of organizations, not workspaces. The tool description adds no clarification beyond the schema, and the mismatch creates confusion.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states verb 'get' and resource 'workspaces' but parameter 'query' is described as filtering organizations, not workspaces, creating confusion. It is distinguishable from siblings like 'zenhub_get_user_workspaces' only by the word 'organization', but no differentiation is provided.

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 on when to use this tool versus alternatives such as zenhub_get_user_workspaces or other workspace-related tools. No prerequisites or context for selecting this tool.

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