Skip to main content
Glama

Botsify

by com.botsify.mcp

Stream builder

stream-builder

Run the streaming agent builder via POST /v1/get-ai-response. Send builder chat messages and receive streamed instruction output.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
extraNoExtra builder payload fields merged into the request
messagesYesBuilder chat messages, usually objects with role and content
stream_idNoClient stream id used to cancel this builder run later

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesJSON or plain text body returned by the Botsify HTTP API

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is not read-only and not idempotent. The description adds the fact it uses POST and is streaming, yielding instruction output. However, it does not explain behavior around cancellation, state persistence, or open-world effects beyond the annotation hints.

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, information-dense sentence, front-loaded with the action. No redundant content or filler.

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?

The tool is moderately complex with nested objects and streaming behavior. The description covers the core purpose but omits relationship to sibling streaming tools, how to consume the stream, and implications of openWorldHint. The output schema exists, so return value explanation is not required, but overall context feels incomplete.

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?

The input schema already describes all three parameters thoroughly (messages array, extra object, stream_id string), achieving 100% coverage. The description does not add any additional parameter-level meaning beyond confirming chat messages are sent.

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?

The description clearly states the tool runs the streaming agent builder via a specific POST endpoint, with action verbs 'Run' and 'Send', and specifies the resource ('agent builder', 'builder chat messages'). It distinguishes from sibling tools like stream-user-message by focusing on builder context and instruction output.

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 such as start-builder-chat or stop-builder-stream. It does not mention exclusions, prerequisites, or scenarios for which the streaming builder is appropriate.

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

All Botsify toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

Several tools have overlapping purposes, such as send-converse-message, send-inbox-message, send-user-message, and stream-user-message, which all deliver messages but with subtle differences. Similarly, list-bot-messenger-users and list-messenger-users both fetch messenger users, and start-builder-chat, clear-builder-conversation, and store-builder-response all manage builder chat state. Descriptions help, but the boundaries are still confusing.

Naming Consistency3/5

Tool names consistently use hyphenated lowercase verb-noun format, but the verbs and nouns vary significantly in specificity. For example, 'get-query-response' vs 'query-mcp-agent' vs 'stream-user-message' all imply querying but with different styles. The pattern is readable but not highly predictable, with some names like 'change-user-activation' and 'patch-instruction-section' deviating from the simple verb_object structure.

Tool Count2/5

With 44 tools, this server feels overloaded. The breadth covers bots, messaging, templates, whitelabel, and versions, but many tools could be consolidated (e.g., multiple message-sending variants). The count exceeds the 25-tool threshold for 'too many', making it difficult for agents to select the right tool without extensive context.

Completeness4/5

The tool set covers the main lifecycle: agent creation, versioning, deployment, deletion, messaging, conversation history, user management, template management, and whitelabel operations. Minor gaps exist, such as missing delete for WhatsApp templates or update operations for user attributes, but these are workable edge cases. Core workflows are well supported.

Resources