Skip to main content
Glama
Sign In
zenhub-mcp

zenhub-mcp

by derekbar90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

zenhub_get_user_organizations

Retrieve all ZenHub organizations accessible to the current user. Optionally filter by search query and limit results.

Instructions

Get all ZenHub organizations accessible to the current user

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_user_organizations"
  }
}

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

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only states 'accessible to the current user', implying auth, but discloses no side effects (should be read-only), no pagination details despite the 'first' parameter, and no rate limit or error behavior. Minimal behavioral disclosure.

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?

A single, clear sentence with no fluff. Every word adds value. Well-structured and front-loaded.

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?

No output schema exists, and the description does not explain the return format (e.g., list of objects with specific fields). For a simple list tool, this may be acceptable, but it omits details like error behavior or what happens when no organizations are found.

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 coverage is 100% (both parameters have descriptions). The description adds no additional meaning beyond the schema—it does not explain formatting, valid values, or interaction between query and first. Baseline score of 3 applies.

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 ('Get') and resource ('organizations'), and clearly indicates scope ('accessible to the current user'). It distinguishes from sibling tools like 'zenhub_get_organization_workspaces' which target workspaces rather than organizations.

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 that this tool is for retrieving a list of organizations accessible to the user, but it does not explicitly state when to use it versus alternatives, or what prerequisites exist (e.g., authentication). No exclusion or when-not-to-use guidance is provided.

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