Skip to main content
Glama
jar285

MCP-Discord

by jar285

test

Verify the MCP-Discord server functionality to ensure proper integration and operation with Discord platforms.

Instructions

A simple test tool to verify the MCP server is working correctly

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the "test" tool. It returns a simple text response confirming that the MCP-Discord server is working correctly.
    case "test": {
      return {
        content: [{ type: "text", text: "MCP-Discord server is working correctly!" }]
      };
    }
  • src/index.ts:188-194 (registration)
    Registration of the "test" tool in the ListTools response. Includes the tool's name, description, and input schema (empty object).
    {
      name: "test",
      description: "A simple test tool to verify the MCP server is working correctly",
      inputSchema: {
        type: "object"
      }
    },
Behavior3/5

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

No annotations are provided, so the description carries full burden. It states the tool is 'simple' and for verification, implying it's likely read-only and safe, but doesn't explicitly confirm this or disclose any behavioral traits like side effects, permissions needed, or response format. It adds minimal context beyond the basic purpose.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core function and appropriately sized for a simple verification tool. Every part of the sentence earns its place by clarifying intent.

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 the tool's low complexity (0 parameters, no output schema, no annotations), the description is complete enough for basic understanding but lacks details on what 'working correctly' means or what the verification entails. It covers the purpose adequately but could benefit from more behavioral context, especially with no annotations to provide safety information.

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?

There are 0 parameters, and schema description coverage is 100%, so the description doesn't need to compensate for undocumented inputs. The baseline for 0 parameters is 4, as no parameter information is required. The description appropriately doesn't mention parameters, focusing on the tool's purpose instead.

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 the tool's purpose: 'to verify the MCP server is working correctly' with the verb 'verify' and resource 'MCP server'. It distinguishes from sibling tools which are all Discord-specific operations, though it doesn't explicitly contrast with them. The purpose is specific and actionable.

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 usage context ('to verify the MCP server is working') but doesn't provide explicit guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, error conditions, or specific scenarios for invocation. The context is clear but lacks detailed when/when-not instructions.

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/jar285/mcp-discord'

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