Skip to main content
Glama

inspect_signal

Read-only

Inspect all enabled channels or one channel in one call to retrieve acquisition freshness, frequency/amplitude readings, probe ratios, unavailable values, and next actions without changing settings.

Instructions

Start here: inspect all enabled channels, or one channel, in one call.

Returns acquisition freshness, frequency/amplitude readings with units, probe ratios, unavailable readings and concrete next actions. No setup, identify, or status call needed. Does not change acquisition or settings. Null readings are not proof of no signal.

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

Input Schema

NameRequiredDescriptionDefault
channelNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and a closed-world scope, and the description adds real interpretive context: what readings come back (freshness, frequency/amplitude with units, probe ratios, unavailable readings, next actions) and the caveat that null readings are not proof of no signal. The 'does not change acquisition or settings' clause matches the read-only annotation rather than contradicting it.

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?

Entry-point instruction is front-loaded in the first clause, and every subsequent sentence adds a distinct piece of information: return content, non-effects, and the null-reading caveat. No filler or repetition of the tool name.

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 one-optional-parameter read tool with annotations and an output schema, nothing an agent needs to call it correctly is missing. The description covers when to call it, what it returns, what it does not do, and how to interpret missing values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single 'channel' parameter only has an integer enum and null default, so the description must carry the meaning. 'All enabled channels, or one channel' explains what the null default versus a supplied channel value actually selects, though it never says what the channel numbers correspond to.

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 ('inspect all enabled channels, or one channel, in one call') and positions itself as the entry point. It also distinguishes itself from siblings by name, noting that no setup, identify, or status call is needed.

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

Usage Guidelines4/5

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

'Start here' plus 'No setup, identify, or status call needed' gives explicit routing guidance and names the alternatives it replaces. It does not explicitly say when to prefer a different tool (e.g. for changing acquisition), though 'Does not change acquisition or settings' implies where the boundary lies.

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