Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

validate_discovery_search_term

Read-only

Validates a Discord discovery search term before use, helping confirm the term is accepted and prevent failed discovery searches.

Instructions

Validate Discovery Search Term. [GET /discovery/valid-term]

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": "validate_discovery_search_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNoterm

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the REST endpoint path, which hints at a remote API call but says nothing about rate limits, what a failed validation looks like, or whether the call has side effects on discovery metadata. That is thin added value beyond the structured fields.

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

Conciseness4/5

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

Two short segments, front-loaded with the tool's purpose and no filler or repetition. It is arguably under-specified rather than verbose, which is a completeness problem rather than a conciseness one.

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?

With no output schema and no explanation of the validation result (boolean? error message? list of violations?), the description leaves the agent unable to predict or use the response. For a tool whose entire value is the verdict it returns, this is a substantial gap.

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

Parameters3/5

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

Schema description coverage is 100% for the single parameter, so the schema already documents 'term'. The description adds no meaning about format, length constraints, or whether the term should be a slug, a partial string, or an exact name. Baseline 3 applies because the schema carries the load.

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

Purpose2/5

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

The description restates the tool name verbatim ('Validate Discovery Search Term') and appends only an HTTP endpoint. It never says what 'validate' means — whether it checks length, profanity, reserved words, or discoverability rules — so an agent cannot distinguish it from the many other validate_* and discovery-related siblings.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no stated relationship to search_discoverable_guilds or search_published_guilds, and no indication of what to do with a valid vs. invalid term. The agent must infer the entire call context from the name alone.

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

Deploy Server

Other Tools