Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

agents_reject_draft

Reject a pending agent draft without sending.

The draft will be marked as rejected and won't be sent. Use this when the generated response isn't appropriate.

Use this when user says:

  • 'Reject this draft'

  • 'Don't send this'

  • 'Cancel this reply'

  • 'Delete this draft'

  • 'This response is wrong'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoOptional reason for rejection (for logging/feedback)
draft_idYesID of the draft to reject
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false, readOnlyHint=false, and idempotentHint=false. The description adds useful context that the draft 'will be marked as rejected and won't be sent,' clarifying the state transition. However, it does not disclose whether rejection is reversible, whether a reason is logged (though schema hints at this), or any permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action in the first sentence, followed by behavioral note and usage examples. The list of user phrasings is somewhat verbose but serves as helpful trigger recognition; overall efficient with no wasted sentences.

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?

Covers the essential action, effect, and when-to-use examples. Minor gaps exist: no mention of irreversibility or alternative tools, but for a simple state-change tool with full schema coverage and annotations, this is largely complete.

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 100%, so all three parameters are already documented in the schema with descriptions. The description adds no new semantic details about parameters beyond what the schema provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (reject) and resource (pending agent draft) with the key scope constraint 'without sending.' An agent can immediately distinguish this from siblings like agents_approve_draft.

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?

Provides clear when-to-use guidance with example user utterances ('Reject this draft', 'Don't send this'). However, it does not explicitly name the alternative (agents_approve_draft) or state when-not-to-use conditions such as rejecting an already-sent message.

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

All dialogbrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources