Skip to main content
Glama
Sign In
discp

discp

by SharimAli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_server_vanity_url

Retrieve the vanity invite URL for a Discord server if enabled, requiring Level 3 boost. Use guild ID or default DISCORD_GUILD_ID.

Instructions

Get the vanity invite URL for a server if enabled (requires Level 3 boost)

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

Input Schema

NameRequiredDescriptionDefault
guildIdNoDiscord server ID (defaults to DISCORD_GUILD_ID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose a meaningful behavioral constraint: the vanity URL only exists if enabled and the server has Level 3 boost. Beyond that it says nothing about permissions required, error vs. null behavior when the condition fails, or the return shape.

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?

One compact sentence with the action first and the condition attached. Nothing is wasted and no restructuring would improve it.

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?

For a one-parameter read tool with no output schema, the description covers what is fetched and the enabling condition. It is adequate but leaves the failure mode (error vs. empty result when the vanity URL is not enabled) unstated, which is the main thing an agent would need before calling it.

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% and the single guildId parameter is fully documented in the schema, including its fallback to DISCORD_GUILD_ID. The description adds no parameter-level meaning, so the baseline 3 applies.

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 states a specific verb and resource ('get the vanity invite URL for a server') and adds a scoping condition ('if enabled'). It is clearly distinguishable from the invite/emoji/member tools around it, though it does not explicitly contrast itself with the nearby invite tools (create_invite, get_invite_details).

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 parenthetical '(requires Level 3 boost)' gives a precondition for when the vanity URL exists, which is real usage context. However, there is no explicit when-to-use guidance, no statement of what happens if the server lacks the boost or has no vanity URL enabled, and no routing to an alternative tool.

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