Skip to main content
Glama
Sign In
BuddyPress MCP Server

BuddyPress MCP Server

by vapvarun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

buddypress_create_message

Create and send private messages between users on a BuddyPress community site. Specify recipients, subject, and content to facilitate user communication.

Instructions

Create a new message

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": {
      "recipients": "<recipients>",
      "subject": "<subject>",
      "message": "<message>"
    },
    "name": "buddypress_create_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
sender_idNoSender user ID (default: current user)
recipientsYesArray of recipient user IDs
subjectYesMessage subject
messageYesMessage content

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Create a new message' implies a write operation, but it doesn't specify permissions required, whether it's idempotent, error conditions, or what happens on success (e.g., returns a message ID). For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, efficient sentence ('Create a new message') that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

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

Completeness2/5

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

Given the complexity of a message creation tool (a mutation with 4 parameters), no annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like authentication needs, error handling, or return values, leaving the agent to guess critical details 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%, with clear descriptions for all 4 parameters (sender_id, recipients, subject, message). The description doesn't add any meaning beyond what the schema provides—it doesn't explain parameter interactions, constraints, or examples. With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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 'Create a new message' clearly states the verb ('Create') and resource ('message'), making the purpose immediately understandable. However, it doesn't distinguish this from sibling tools like 'buddypress_delete_message' or 'buddypress_get_message', which would require mentioning it's specifically for creating (not retrieving or deleting) messages.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., user authentication), when not to use it (e.g., for retrieving messages), or how it relates to sibling tools like 'buddypress_list_messages' or 'buddypress_delete_message'. The agent must infer usage from the name alone.

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