Skip to main content
Glama

Synoptic

by com.synoptic
OverviewDiscussionsAdmin

Create draft stream

create_stream

Create a free draft publishing stream owned by the signed-in user for their research, news, or other updates. Supply a plain-text description and add a first post with create_stream_post before publishing with publish_stream. This creates a publishing destination; use existing custom-target tools to configure supported source monitoring or request_stream to request new coverage. Does not configure paid pricing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesStream name shown in the catalog and on its page.
labelNoShort tag shown on the stream page; empty for none.
streamTypeNoPUBLIC streams are listed in the public catalog once published; PRIVATE streams are visible only to their owner and to users who follow, subscribe to, were invited to, or have organization access to them. update_stream can’t change it.PUBLIC
descriptionYesWhat the stream publishes, as plain text; Markdown is not rendered.
streamCategoryNoTopic category; stream list tools can filter by it.OTHER
apiAccessEnabledNoWhether external API consumers can subscribe to this stream.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
streamYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / streamType / description
      Previous value: -"PUBLIC streams are listed in the public catalog once published; PRIVATE streams are visible only to their owner and to invited, subscribed or organization users. update_stream can’t change it."New value: +"PUBLIC streams are listed in the public catalog once published; PRIVATE streams are visible only to their owner and to users who follow, subscribe to, were invited to, or have organization access to them. update_stream can’t change it."
  2. Changed6 schema fields changed
    • addedInput schema / properties / apiAccessEnabled / description
      Added value: +"Whether external API consumers can subscribe to this stream."
    • addedInput schema / properties / description / description
      Added value: +"What the stream publishes, as plain text; Markdown is not rendered."
    • addedInput schema / properties / label / description
      Added value: +"Short tag shown on the stream page; empty for none."
    • addedInput schema / properties / name / description
      Added value: +"Stream name shown in the catalog and on its page."
    • addedInput schema / properties / streamCategory / description
      Added value: +"Topic category; stream list tools can filter by it."
    • addedInput schema / properties / streamType / description
      Added value: +"PUBLIC streams are listed in the public catalog once published; PRIVATE streams are visible only to their owner and to invited, subscribed or organization users. update_stream can’t change it."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations cover the safety profile (non-read-only, non-destructive, non-idempotent, closed-world). The description adds that the result is a draft, that ownership is bound to the signed-in user, that the stream is free, and that paid pricing is out of scope — context not present in the annotations. It stops short of stating auth/permission requirements or duplicate-name behavior.

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?

Three sentences, front-loaded with the core action before the workflow and exclusions. Dense but every sentence carries routing or constraint information; the middle sentence about custom-target tools is the most compressed.

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?

With an output schema present, return values need not be described. The description covers the create-publish lifecycle, ownership, and scope exclusions, which is sufficient for a creation tool whose annotations and schema carry the rest.

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%, so all six parameters including the two enums are already documented. The description only reinforces that the description field is plain text (Markdown not rendered), adding marginal value beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 and resource — create a free draft publishing stream owned by the signed-in user — plus the scope (research, news, other updates). It distinguishes itself from publish_stream and request_stream, so an agent can tell it apart from siblings without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit workflow: add a first post with create_stream_post, then publish with publish_stream. It also names alternatives and exclusions — existing custom-target tools for source monitoring, request_stream for new coverage, and 'does not configure paid pricing'.

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

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