Skip to main content
Glama

Zendesk

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

Schema Changelog

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

  1. Added

TDQS

A5/5.0
Behavior5/5

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

Discloses multi-source fan-out (SEC EDGAR, GDELT→GNews fallback, USPTO), handling of rate limits/errors, and the USPTO PatentsView API sunset. Also describes return structure (changes[] grouped by source, total_changes count, citation URIs). No contradiction 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?

Description is well-structured with front-loaded examples, clear explanations, and no wasted words. Every sentence serves a purpose.

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?

Describes return structure despite no output schema. Covers source details, failure modes, and typical usage patterns. Complete for a tool of this complexity.

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

Parameters5/5

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

All three parameters are described with additional context beyond the schema: type constrained to 'company', since with examples and common usage, value explaining ticker or CIK. Schema coverage is 100%, and description adds meaningful guidance.

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?

Description clearly states the tool provides a change feed for a company in a specified window. Uses colloquial examples like "What's new with X" and explicitly distinguishes from sibling tool entity_profile.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use this tool vs entity_profile. Includes examples of acceptable since values (ISO date and relative shorthand) and typical monitoring recommendation ("30d" or "1m").

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