Skip to main content
Glama

Zendesk

by io.github.pipeworx-io

Pipeworx Trending

pipeworx_trending
Read-onlyIdempotent

What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice before asking your own question, (3) seeing whether your use case aligns with what most agents need. Self-aggregating signal — derived from CF analytics-engine, no PII, just (pack, tool, count). Cached 5min-1h depending on window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNo24h (default) | 7d | 30d. Shorter windows surface what's hot right now; longer windows show steady-state demand.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds valuable behavioral details: caching (5min-1h), data source (CF analytics-engine), no PII, and the exact output structure (pack, tool, count). No contradictions with annotations.

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 well-structured: starts with the core purpose, lists use cases, then provides technical details. Every sentence adds value. No fluff. Length is appropriate for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description sufficiently explains the return shape (top tools, top packs, total call volume). It covers caching, data source, privacy, and window semantics. For a simple tool with one optional parameter, this is fully complete.

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

Parameters4/5

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

Schema coverage is 100% with a description for the 'window' parameter. The description adds strategic guidance: 'Shorter windows surface what's hot right now; longer windows show steady-state demand.' This provides meaning beyond the enum values and schema description.

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 clearly states what the tool does: returns top tools, top packs, and total call volume over recent windows. It uses specific verbs like 'returns' and specifies the resource (trending data on Pipeworx). The description distinguishes it from siblings like 'discover_tools' by focusing on aggregated trending signals rather than listing all tools.

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

Usage Guidelines4/5

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

The description explicitly lists three concrete use cases (discovering hot data sources, confirming a popular tool, aligning use case with needs). It provides context on when to use shorter vs longer windows. However, it does not explicitly state when NOT to use this tool or mention alternatives.

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

All Zendesk toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0
Disambiguation2/5

Many tools have overlapping purposes, especially the Pipeworx query tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim) which all provide factual answers, making it unclear which to use. The set also mixes Zendesk tools with a large number of prediction market and data tools, creating confusion.

Naming Consistency2/5

Naming conventions are inconsistent: Zendesk tools use 'zd_' prefix, Pipeworx tools use various prefixes like 'ask_', 'bet_', 'compare_', etc., and some are named with full words. There is no uniform pattern across the set.

Tool Count2/5

35 tools is high for a server named 'Zendesk', especially since only 5 are Zendesk-specific. The majority are unrelated to Zendesk, indicating the tool count is inappropriate for the implied purpose.

Completeness1/5

For a Zendesk server, the tool set is severely incomplete, offering only basic CRUD operations (get, list, search for tickets and users). Missing essential Zendesk features like ticket creation, update, delete, or macros, while containing many irrelevant tools from other domains.

Resources