Skip to main content
Glama

Pause Stream

pause_stream
Idempotent

[Act · writes] Pause a stream so it stops running on its cron schedule. Existing posts remain in the library. Use resume_stream to re-enable it. own_profile streams are billing-managed and cannot be paused here.

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": {
      "stream_id": "<stream_id>"
    },
    "name": "pause_stream"
  }
}

Input Schema

NameRequiredDescriptionDefault
stream_idYesStream ID from list_streams

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description still adds genuinely non-obvious context: existing posts are preserved, the pause targets the cron schedule rather than content, and own_profile streams are ineligible. It stops short of saying whether an in-flight run is aborted or what state/response is returned.

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?

Four short sentences, front-loaded with the action tag and the core effect, then side effects, then the alternative, then the exclusion. No sentence is redundant.

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?

For a one-parameter mutation with annotations and no output schema, the description covers effect, preserved data, and eligibility constraints. Only the post-call state (return value, whether a currently running execution is interrupted) is left unspecified, which is minor at this complexity.

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% and the single parameter is documented as 'Stream ID from list_streams', which even points at the sibling used to obtain it. The description adds no further meaning about stream_id, so the high-coverage baseline of 3 applies.

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 ('Pause a stream') plus the precise mechanism affected ('so it stops running on its cron schedule'). The '[Act · writes]' tag and the explicit contrast with resume_stream let an agent distinguish it from siblings without opening a 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 when-to-use (stop the cron schedule), a named alternative for the inverse action ('Use resume_stream to re-enable it'), and an explicit exclusion ('own_profile streams are billing-managed and cannot be paused here'). That is the full when / alternative / when-not triad.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources