Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_profile

Read-only

Fetch a Discord guild profile by server ID to review its details for moderation, configuration, or account automation.

Instructions

Get Guild Profile. [GET /guilds/{guild_id}/profile]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "guild_id": "<guild_id>"
    },
    "name": "get_guild_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only a REST path, which hints at the underlying API but says nothing about auth requirements, rate limits, or what the 'profile' contains versus a full guild object.

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, front-loaded fragments with no filler; the resource comes first and the endpoint path is supplementary. It is efficient but so terse that it borders on under-specification rather than demonstrating strong structure.

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 single-parameter read tool with complete schema coverage, full safety annotations, and no output schema, the minimum bar is met. The remaining gap is disambiguation from get_guild and get_guild_preview, which the description does not address and which an agent needs in order to choose correctly.

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?

There is a single required guild_id parameter with 100% schema description coverage ('Server (guild) ID'), so the schema already carries parameter meaning. The description adds nothing beyond it, which is the expected baseline given complete schema coverage.

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

Purpose3/5

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

The description pairs a specific verb with a resource ('Get Guild Profile') and adds the REST endpoint path, so the agent knows it fetches a guild's profile object. However, it gives no way to distinguish this from siblings like get_guild, get_guild_preview, or get_user_profile, which all sound like plausible reads of the same object.

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 at all: no stated conditions, no exclusions, and no mention of the sibling tools that fetch adjacent guild data. The agent must infer selection purely from the name.

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