Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_set_pronouns

Set or clear profile pronouns on a Discord user account. Provide the pronoun text to display, or pass an empty string to remove existing pronouns.

Instructions

Set profile pronouns. Empty string clears them.

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": {
      "pronouns": "<pronouns>"
    },
    "name": "discord_set_pronouns"
  }
}

Input Schema

NameRequiredDescriptionDefault
pronounsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the non-obvious clearing behavior via empty string, which is genuinely useful. However, it says nothing about permissions required, whether it affects only the calling user's profile, rate limits, or what the response contains for a mutation tool.

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?

Two short sentences, front-loaded with the action and followed immediately by the edge-case behavior. No filler or redundancy.

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 setter with no annotations and no output schema, the description covers purpose and the clear case but omits scope (own profile only) and value format. It is adequate to invoke the tool but leaves the agent guessing on input shape.

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 coverage is 0% and the single parameter is only typed as a string with maxLength 40, so the description must compensate. It does explain the empty-string sentinel, but leaves the expected format (single value vs. slash-separated pronoun sets) and the 40-character limit unaddressed.

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?

States a specific verb and resource ("Set profile pronouns") that an agent can distinguish from siblings like discord_set_about_me or discord_set_nickname. It does not explicitly name a sibling or scope (own profile vs. other), but the resource is unambiguous.

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?

Usage is implied by the verb and the note that an empty string clears pronouns, which tells the agent how to remove them. There is no explicit when-to-use guidance, no mention of prerequisites, and no routing to alternatives such as discord_clear_status for other profile fields.

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