Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_integration_application_ids

Read-only

Fetches integration application IDs for the current user’s Discord guilds, helping identify which applications are linked to each server.

Instructions

Get Guild Integration Application IDs. [GET /users/@me/guilds/integration-application-ids]

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_guild_integration_application_ids"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 covered. The description adds nothing beyond the endpoint path (which is essentially redundant with readOnlyHint) — no statement about auth requirements, result shape, pagination, or what the IDs represent.

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

Conciseness3/5

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

It is a single short sentence with no filler, so it is not bloated. However, its brevity comes from under-specification rather than density — it spends its one sentence echoing the title plus an endpoint tag.

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 parameters, the description was the only place to explain what the returned application IDs mean and in what structure, and it does not. For an open-world read tool whose output is entirely undocumented, this leaves a material gap.

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?

The tool takes zero parameters, so there is no parameter semantics to document; the baseline for a 0-parameter tool is 4. Nothing in the description contradicts the empty schema.

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 restates the tool name ('Get Guild Integration Application IDs') and adds only the HTTP endpoint path. The endpoint ('/users/@me/guilds/...') does clarify that the scope is the current user's guilds, but 'integration application IDs' remains undefined — it never says whether this returns a list of IDs, a mapping, or IDs for which integrations.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no mention of related siblings such as get_application or get_guild_integration_application_ids-adjacent lookups. The agent must infer usage entirely 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