Skip to main content
Glama

pause_signal

Pause a signal and return it. A paused signal is not checked and spends nothing; its events stay available in get_signal_events, and it does not count toward the active signal limit. Pausing an already paused signal changes nothing and succeeds. Resume it with resume_signal. Fails with signalNotFound for an unknown id and with signalStopped for a stopped signal.

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": {
      "signalId": "<signalId>"
    },
    "name": "pause_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
signalIdYesSignal id, as returned by create_signal or get_signals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and openWorldHint=true, but the description adds substantial behavior: the signal is no longer checked, spends nothing, keeps events readable via get_signal_events, and is excluded from the active signal limit. It also discloses idempotency semantics and the exact error codes signalNotFound and signalStopped, which goes well beyond the structured fields.

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, each carrying distinct information (effect, state semantics, idempotency, inverse tool, failure modes), with the core action front-loaded and no filler or repetition of the schema.

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?

For a single-parameter mutation with no output schema, the description covers the effect on billing, event retention and limits, idempotency, the inverse tool, and both error conditions — nothing an agent needs to invoke it correctly is missing.

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 signalId parameter is already documented as coming from create_signal or get_signals, so the schema carries the parameter burden. The description only adds that an unknown id yields signalNotFound, which is useful but marginal; baseline 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 signal') plus the side effect of returning the signal object, and explicitly names the inverse operation resume_signal so an agent can distinguish the pair without opening either 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 the positive case (pause to stop checking/spending while keeping events), the inverse alternative ('Resume it with resume_signal'), and the edge conditions (already-paused is a no-op success; stopped signals fail with signalStopped), so an agent knows both when to call it and when the call is pointless.

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.