Skip to main content
Glama
Sign In
zenhub-mcp

zenhub-mcp

by derekbar90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

zenhub_query_potentially_dangerous

Run custom GraphQL queries for actions not available in standard tools. Mutations require your explicit approval.

Instructions

FALLBACK: Execute custom GraphQL queries when specific tools don't meet your needs. IMPORTANT: Mutations but have EXPLICT appoval from the user by repeating back a super minimal confirmation message.

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": {
      "query": "<query>"
    },
    "name": "zenhub_query_potentially_dangerous"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesGraphQL query to execute
variablesNoVariables for the GraphQL query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.8

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It alerts that mutations require explicit user approval, which is crucial. However, it does not describe other behaviors like rate limits, error handling, or read-only query effects.

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 concise with two sentences, front-loading the purpose. Typos ('EXPLICT', 'appoval') slightly reduce clarity but do not majorly hinder understanding.

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?

Given no annotations and no output schema, the description covers the mutation safety aspect but omits return format, error handling, and parameter format details. It is adequate but incomplete for safe usage.

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% with brief descriptions for both parameters. The description adds no additional meaning beyond the schema, meeting the baseline for high coverage.

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 it executes custom GraphQL queries as a fallback when specific tools don't meet needs. This distinguishes it from sibling tools, though not explicitly naming them.

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 using it only when other tools fail, but does not give explicit when-not-to-use or mention alternatives. The mutation approval warning provides some guidance.

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