mcp-discord-bridge

get_member

Retrieve detailed information about a specific Discord guild member using their user ID and guild ID.

Instructions

Get detailed information about a specific guild member

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": {
      "guild_id": "<guild_id>",
      "user_id": "<user_id>"
    },
    "name": "get_member"
  }
}

Input Schema

Name	Required	Description	Default
`guild_id`	Yes
`user_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 25, 2026

TDQS

B3.1/5.0

Behavior3/5

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

The description implies a read-only operation ('Get detailed information'), which is straightforward. However, with no annotations, it does not disclose any behavioral traits like authentication needs, rate limits, or whether the member must be in the guild. It is adequate but not detailed.

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?

The description is a single sentence with no unnecessary words. It is efficient and to the point.

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?

Given the simplicity of the tool (2 parameters, no output schema), the description is minimally complete. It indicates what the tool does but does not explain the return format or any nuances. For a simple getter, this is adequate but could be improved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not explain the purpose or format of the parameters. It mentions 'guild member' but does not describe what 'guild_id' or 'user_id' represent or where to find them. With 0% schema coverage, the description fails to compensate.

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?

The description clearly states 'Get detailed information about a specific guild member', which identifies the action and resource. It distinguishes from sibling tools like 'list_members' (which lists all) or modifying tools, but could be more explicit about what 'detailed information' includes.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not mention that this should be used when you need data for a single member, while 'list_members' is for all members.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.