Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_set_about_me

Set or clear the Discord account bio by providing a bio string; pass an empty string to remove the current bio.

Instructions

Set the account bio. Empty string clears it.

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": {
      "bio": "<bio>"
    },
    "name": "discord_set_about_me"
  }
}

Input Schema

NameRequiredDescriptionDefault
bioYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose an important non-obvious behavior: passing an empty string clears the bio, which is real value beyond the schema. However, it says nothing about permissions/authentication, rate limits, or whether the change is immediately visible or reversible.

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 terse sentences, front-loaded with the action and followed immediately by the edge-case behavior. Nothing is wasted and nothing needs reordering.

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?

For a one-parameter setter with no annotations and no output schema, the description covers what it does and the key edge case. Missing only secondary context such as permission requirements, which is a modest gap rather than a blocking one.

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?

Schema coverage is 0%, so the description must compensate, and it does so for the single parameter by explaining the special empty-string value semantics that the bare schema (string, maxLength 190) cannot convey. It does not restate the 190-character limit, but the schema already covers that.

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 the account bio"), which is enough to separate it from sibling profile-setter tools like discord_set_pronouns or discord_set_global_name. It stops short of explicitly naming those siblings or drawing the boundary, so it is clear but not maximally differentiated.

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?

The description implies when to use it (to set the account bio) and gives one concrete operational rule, that an empty string clears the field. It offers no explicit exclusions or pointers to related profile tools, so guidance is implied rather than spelled out.

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