Skip to main content
Glama
JurreBrandsenInfoSupport

Zendesk API MCP Server

support_info

Retrieve essential support system information from Zendesk to access configuration details and system status for managing customer support operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the 'support_info' tool logic. It returns a placeholder message about Zendesk Support configuration, with error handling.
    handler: async () => {
      try {
        // This would typically call an endpoint like /api/v2/account/settings
        // For now, we'll return a placeholder message
        return {
          content: [{ 
            type: "text", 
            text: "Zendesk Support information would be displayed here. This is a placeholder for future implementation."
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error getting support info: ${error.message}` }],
          isError: true
        };
      }
    }
  • Export of supportTools array that defines and registers the 'support_info' tool with its name, description, empty schema, and handler.
    export const supportTools = [
      // This is a placeholder for additional Support-specific tools
      // Most Support functionality is covered by the other tool modules
      {
        name: "support_info",
        description: "Get information about Zendesk Support configuration",
        schema: {},
        handler: async () => {
          try {
            // This would typically call an endpoint like /api/v2/account/settings
            // For now, we'll return a placeholder message
            return {
              content: [{ 
                type: "text", 
                text: "Zendesk Support information would be displayed here. This is a placeholder for future implementation."
              }]
            };
          } catch (error) {
            return {
              content: [{ type: "text", text: `Error getting support info: ${error.message}` }],
              isError: true
            };
          }
        }
      }
    ];
  • src/server.js:47-52 (registration)
    MCP server registration loop that registers all tools including 'support_info' from supportTools by calling server.tool() for each.
    // Register each tool with the server
    allTools.forEach((tool) => {
      server.tool(tool.name, tool.schema, tool.handler, {
        description: tool.description,
      });
    });
  • src/server.js:19-19 (registration)
    Import of supportTools into the main server file for aggregation and registration.
    import { supportTools } from "./tools/support.js";
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JurreBrandsenInfoSupport/zendesk-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server