Zendesk MCP Pack — tickets, users, organizations via OAuth.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 41 tools
The tool set contains several overlapping query/retrieval tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions) that an agent could easily confuse, and multiple prediction-market analysis tools with similar purposes. The handful of Zendesk tools are distinct, but the overall set has unclear boundaries among many data-lookup and research tools.
Naming conventions are inconsistent: most tools use snake_case with varying verb-noun or noun-verb patterns (ask_pipeworx, compare_entities, entity_profile, resolution_audit), while Zendesk tools use a zd_ prefix with different structures (zd_get_ticket, zd_list_users). Some names are vague (remember, recall, forget, subscribe) and don't follow a predictable pattern.
41 tools is a large number, and the count is especially inappropriate given the server is named 'Zendesk'—only 5 of 41 tools relate to Zendesk, while the rest are a broad Pipeworx data/prediction-market toolkit. This mismatched scope makes the tool count feel excessive and unfocused for the apparent purpose.
For a server named Zendesk, the tool surface is severely incomplete: it only provides read operations (get ticket, list tickets, get user, list users, search tickets) with no create, update, delete, or comment operations. The unrelated Pipeworx tools are extensive, but the Zendesk domain itself has major dead ends.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
company_facts1 field changedInput schema / properties / exclude_publishersAdded value: +{
+ "description": "Publisher ids forbidden for fact retrieval: sec, fmp, alphavantage. Case and surrounding whitespace are normalized; unknown ids are refused. Excluding sec currently leaves no eligible fact source and returns unavailable/sources_excluded with the selection reasons. Identity and fiscal-calendar lookups may still use SEC; no excluded financial concept is fetched.",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}company_factskalshi_weather_edgerelease_calendar_marketsresolution_auditresolution_diffbet_research2 fields changedInput schema / examplesPrevious value: -[
- {
- "market": "when-will-bitcoin-hit-150k"
- },
- {
- "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
- }
-]New value: +[
+ {
+ "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ },
+ {
+ "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ }
+]Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."bet_research2 fields changedInput schema / examplesPrevious value: -[
- {
- "market": "will-bitcoin-reach-100k-in-july-2026"
- },
- {
- "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
- }
-]New value: +[
+ {
+ "market": "when-will-bitcoin-hit-150k"
+ },
+ {
+ "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+ }
+]Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."polymarket_kalshi_spread2 fields changedInput schema / examplesPrevious value: -[
- {
- "topic": "fed"
- },
- {
- "topic": "btc"
- }
-]New value: +[
+ {
+ "topic": "fed"
+ },
+ {
+ "topic": "btc"
+ },
+ {
+ "topic": "bitcoin"
+ },
+ {
+ "topic": "fed rate decision"
+ }
+]Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."Freshdesk MCP Pack — helpdesk ticket and contact management via Freshdesk API v2.
Intercom MCP Pack — contacts, conversations, companies via OAuth.
Calendly MCP Pack — wraps the Calendly API v2 for scheduling data.
Add one secure layer between your agents and this server.