Skip to main content
Glama

Get status

get_status
Read-onlyIdempotent

Check iMessage bridge health and settings, including version, live watch status, last inbound time, sending state, allowlist size, and remaining send budget without exposing message content.

Instructions

Returns the health and settings of the iMessage bridge: imsg version, whether the live watch is healthy, the last inbound message time, whether sending is on, the allowlist size and the send budget left. Contains no message content.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: exactly what state is reported (watch health, send budget remaining, allowlist size) and the explicit privacy guarantee that it contains no message content, which is a meaningful behavioral trait for an agent deciding whether to call it.

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?

A single front-loaded sentence that names the resource first and then lists fields; the colon-delimited enumeration is easy to scan. It is dense but every listed field earns its place, and there is no filler.

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 must carry the return-value burden itself, and it does so by enumerating the reported fields plus the no-content caveat. What remains unstated is error behavior (e.g. what 'unhealthy' looks like) and whether the budget figure is a raw count, but for a zero-parameter status probe this is close to complete.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The enumerated return fields serve as useful orientation even though they are technically output rather than input semantics.

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 ('Returns the health and settings of the iMessage bridge') and enumerates the exact fields returned (imsg version, watch health, last inbound time, sending on/off, allowlist size, send budget). That field list makes it unmistakable against siblings like get_messages or list_chats, though it never names an alternative explicitly.

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: an agent can infer this is a diagnostics/health-check probe, but there is no statement of when to prefer it over check_new_messages or get_messages, and no preconditions are given. Adequate but leaves routing to inference.

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