Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

set_my_app_role_connection

Updates the current user's linked application role connection for a specified Discord app, setting platform name, username, and metadata.

Instructions

Modify User Application Role Connection. [PUT /users/@me/applications/{application_id}/role-connection]

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": {
      "application_id": "<application_id>"
    },
    "name": "set_my_app_role_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
metadataNometadata
platform_nameNoplatform name
application_idYesApplication (app/bot) ID
platform_usernameNoplatform username

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description's one piece of added value is the PUT endpoint, which signals replace-style semantics rather than a patch. It does not say what happens to omitted metadata fields, whether existing values are wiped, or what auth scope is required.

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 terse fragments that are front-loaded with the action and resource. Nothing is padded or redundant. The bracketed HTTP route is the only borderline item, though it usefully implies replace semantics.

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

Completeness5/5

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

This is a focused mutation tool with only four parameters and an output schema is absent, so the description does not need to explain return values. The PUT route already communicates that the operation replaces the user's application role connection. However, it does not state that the metadata object is free-form key/value data or what the app needs to be authorized for, which matters for correct invocation.

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%, so application_id, platform_name, platform_username, and the nested metadata map are already documented structurally, and the baseline of 3 applies. The description adds no meaning beyond the schema, notably nothing about what keys belong in the free-form metadata object. With full coverage, the schema carries the load and no penalty is warranted.

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?

Names a specific verb ("Modify") and a specific resource ("User Application Role Connection"), which is enough to distinguish it from the guild-role and user-connection siblings. The bracketed PUT endpoint reinforces that it targets the current user's app role connection record. It stops short of explaining what a role connection actually contains, so the purpose is clear but shallow.

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 statement of when to use this instead of the obvious counterparts like get_my_app_role_connection, list_my_app_role_connections, or set_role_linked_requirements. No prerequisites (such as an OAuth scope on the application) are mentioned. The agent must infer from the tool name alone that this is the write path for the read tools.

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