Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by cappyeo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

application_modify_role_connection_metadata

Idempotent

Replace role connection metadata for a Discord app, removing any existing records not included. Returns the updated records and count.

Instructions

Purpose: Replace the application role-connection metadata records (max 5).

This is a wholesale replace - any existing record not in records is removed.

Returns: {records, count} after the update.

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>",
      "records": "<records>"
    },
    "name": "application_modify_role_connection_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordsYesUp to 5 metadata records - wholesale replace.
application_idYesBot/app application ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.22.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint false, destructiveHint false), the description adds key behavioral context: this is a wholesale replace, records are removed, and it returns '{records, count}'. This fully informs the agent of the side effects and result shape, exceeding what annotations alone provide.

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?

Three bolded sections in under 25 words: purpose, behavior warning, and return value. Each sentence earns its place, front-loaded with the core purpose, and there is no fluff.

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

Completeness4/5

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

The description covers the essential behavioral aspects (replace, removal, max 5, return shape) and the schema covers parameter details. It doesn't mention permissions or auth requirements, but for a two-parameter tool with a well-specified schema, it is nearly complete. The output schema signal also reduces the need to explain return values.

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 the baseline is 3. The description adds the 'wholesale replace' context but doesn't elaborate on individual parameters beyond what the schema already describes. It does reinforce that `records` is the replacement set, adding minor value.

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

Purpose5/5

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

The description opens with 'Replace the application role-connection metadata records' – a clear verb and resource. It further specifies a 'wholesale replace' semantics, distinguishing it from get/partial-update operations and aligning with the sibling tool application_get_role_connection_metadata.

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

Usage Guidelines4/5

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

The description clearly warns that 'any existing record not in records is removed', which is critical usage guidance for preserving existing entries. It does not name alternative tools explicitly, but the replace-vs-get distinction is clear and the behavior is unambiguous.

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