dynamic-discord-bot-api-mcp

discord_search_endpoints

Read-only

Search cataloged Discord Bot HTTP API endpoints using fuzzy keywords to find the endpoint you need.

Instructions

Fuzzy-search cataloged Discord Bot HTTP API endpoints.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discord_search_endpoints"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`search`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 17, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds the 'fuzzy-search' behavior and the fact that it searches a catalog, which is useful context. However, it doesn't disclose result format, sorting, or any limitations of the fuzzy search.

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 sentence, extremely concise, with the key verb and resource front-loaded. Every word earns its place, making it an efficient statement.

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

Completeness2/5

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

Given the tool's simplicity, the description is still incomplete: it omits parameter semantics, return value expectations, and any usage context relative to siblings. With zero schema property descriptions and no mention of search/limit, the agent cannot optimally select or invoke this tool without additional inference.

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

Parameters2/5

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

Schema description coverage is 0%, and the description never mentions the 'search' or 'limit' parameters. The word 'fuzzy-search' implies the search parameter's role, but 'limit' is entirely unexplained. The description provides no meaningful parameter information beyond what the schema exposes (types/defaults).

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 uses the specific verb 'fuzzy-search' and identifies the resource as 'cataloged Discord Bot HTTP API endpoints,' clearly distinguishing it from sibling tools like discord_get_endpoint and discord_call_endpoint by focusing on search over a static catalog.

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 provides no explicit guidance on when to use this tool versus alternatives. The sibling list is present, but the description doesn't state e.g., 'Use this to discover endpoints before calling them with discord_call_endpoint.' Usage is only implied by the tool name.

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

Deploy Server