Skip to main content
Glama

get_signals

Read-only

List the account's signals (created with create_signal). Each signal has id (pass it as signalId to the other signal tools), type, its target fields, label, status, stoppedReason, createdAt, baselineAt (when the first check completed, or null until then), lastCheckedAt and nextCheckAt (the planned next check, or null when the signal is not active; your workflows and working hours can move it). status is active (checked on schedule), paused, or stopped: Linked API stopped checking because the target can no longer be watched, and stoppedReason is targetNotFound or watchPeriodEnded. A stopped signal cannot be resumed; delete it and create it again.

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": "get_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional. Return only signals of this type.
statusNoOptional. Return only signals with this status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

The annotations only declare readOnly and openWorld; the description goes well beyond them, explaining status transitions, the stoppedReason values (targetNotFound, watchPeriodEnded), that a stopped signal cannot be resumed, and that workflows/working hours can shift nextCheckAt. That is exactly the operational context an agent needs before deciding what to do with a returned signal.

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?

Front-loaded with the verb and resource, then dense but purposeful field documentation; every clause about status and stoppedReason earns its place. The single long sentence structure makes it slightly harder to scan than separate sentences would.

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?

With no output schema, the description takes on the full burden of describing the returned object's fields and their null semantics, and it does so completely, including lifecycle rules for stopped signals. Nothing material about calling or interpreting the result 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 both filter parameters carry enum descriptions, so the description need not restate them. The one extra semantic it adds is that the returned id should be passed as signalId to other signal tools, which is useful but does not map to either input parameter.

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?

States a specific verb and resource ('List the account's signals'), scopes it to the account, and ties it to its creator (create_signal). It does not explicitly distinguish itself from the sibling get_signal, so an agent must infer that this is the collection-level read.

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?

Usage is only implied: 'List' plus the two optional filters suggests enumeration, and 'pass it as signalId to the other signal tools' hints at the workflow. There is no explicit statement of when to call this versus get_signal or get_signal_events.

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.