Skip to main content
Glama

Edit own discussion post

bb_edit_discussion_post
Idempotent

Edit an authored Blackboard discussion post when the forum permits changes, requiring write access and explicit confirmation.

Instructions

Edit a post you authored, where the forum allows edits. Requires BB_ALLOW_WRITES=1 and confirm:true.

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": {
      "courseId": "<courseId>",
      "forumId": "<forumId>",
      "messageId": "<messageId>",
      "body": "<body>"
    },
    "name": "bb_edit_discussion_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
boardIdNo
confirmNo
forumIdYes
courseIdYes
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare it is a non-destructive, idempotent write; the description adds real behavioral context by disclosing the server-side write gate (BB_ALLOW_WRITES=1) and the confirm:true requirement, plus the forum-level editability constraint. It does not say what happens to the post on partial edits or what the response contains, but the added gating detail goes well beyond the annotations.

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 ownership/forum constraint and followed by the operational gate. No padding or repetition.

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 mutation tool with no output schema and zero parameter documentation, the description covers the critical gating behavior but leaves the call shape under-specified — an agent still cannot tell what body should contain or how the identifiers relate. Adequate on safety, incomplete on invocation.

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?

Schema description coverage is 0% across six parameters, and the description explains only confirm (that it must be true). The meaning of body (presumably the new content), boardId, courseId, forumId, and messageId is left entirely to inference — notably the required ones — so the description does not compensate for the coverage gap.

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 (edit a discussion post) and narrows scope to posts the caller authored. It implicitly separates itself from bb_delete_discussion_post and bb_reply_to_discussion, though it does not name an alternative when the edit is not permitted.

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?

Gives two concrete preconditions for use: the post must be self-authored and the forum must allow edits. It stops short of stating what to do when those conditions fail (no fallback or alternative tool named), so guidance is clear but not exhaustive.

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