Skip to main content
Glama

get_signal

Read-only

Get one signal by its id, in the same shape as get_signals returns it: status, stoppedReason, baselineAt, lastCheckedAt, nextCheckAt, target fields and label. Fails with signalNotFound when the account has no signal with this id.

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": "get_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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine value by naming the failure mode ('Fails with signalNotFound when the account has no signal with this id') and enumerating returned fields, though it says nothing about permissions, freshness, or pagination-like concerns.

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?

Two tight sentences, front-loaded with the action, then the return shape, then the error case. No filler or redundant restatement of the name.

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 no output schema, the description usefully sketches the returned fields and ties them to get_signals' shape, plus it covers the not-found path. The field list is partial ('target fields and label'), which keeps it just short of complete.

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 signalId property already documents that ids come from create_signal or get_signals, so the description's mention of provenance merely echoes the schema. No additional format, constraints, or lookup semantics are contributed.

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 ('Get one signal by its id') and immediately distinguishes itself from the bulk sibling by saying the result comes back 'in the same shape as get_signals returns it.' An agent can tell single-record fetch from list fetch 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 Guidelines3/5

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

Usage is implied rather than stated: 'by its id' and the reference to create_signal/get_signals as the source of ids tell the agent when this tool applies, but there is no explicit statement of when to prefer get_signals or get_signal_events instead.

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.