Skip to main content
Glama
Sign In

BumbleBox

by ai.bumblebox
OverviewDiscussionsAdmin

Campaign replies waiting for the user

list_replies_to_validate
Read-only

Replies received on campaigns that still need the user: prepared reply drafts waiting for validation, and replies with no answer yet (with the stored AI triage: kind, summary, whether a human is needed).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_replies_to_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
draftsYes
pendingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this as a read-only, non-open-world tool, and the description adds useful behavioral detail by saying it returns prepared drafts and replies with stored AI triage fields (`kind`, `summary`, whether a human is needed). It does not discuss ordering, pagination, or limits, but with annotations covering safety and an output schema present, the added context is solid.

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 definition is a single front-loaded sentence with a colon-delimited breakdown of the two reply categories. It is dense but every clause contributes to scope or return-content understanding.

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

Completeness5/5

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

Given the read-only annotations, empty parameter schema, and existing output schema, the description provides enough context about what the tool surfaces and why those items are grouped together. Nothing critical for correct invocation is missing.

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?

This tool has zero parameters and 100% schema description coverage, so parameter semantics are not a concern. The description appropriately does not spend space explaining nonexistent inputs.

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 the verb and resource: listing replies on campaigns that still need the user, including drafts awaiting validation and unanswered replies. It is specific about the two included categories, but it does not explicitly distinguish this tool from the sibling `list_to_answer`, which appears closely related.

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 phrase 'still need the user' and the inclusion of 'prepared reply drafts waiting for validation' imply when to use the tool. However, there is no explicit when-to-use guidance or comparison against alternatives such as `list_to_answer`, so usage must be inferred from the returned-content description.

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

All BumbleBox 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