Skip to main content
Glama
agentisend

agentisend

Get kill switch state

get_kill_switch_state
Read-onlyIdempotent

Check whether a sending key is paused, when it stopped, and why—use this when a send fails with kill_switch_active. It also returns where a person can undo the pause.

Instructions

Purpose: find out whether this key is stopped, since when, and the reason recorded. Read it when a send fails with kill_switch_active. NOT for: lifting it. Nothing here can; a person resumes a key in the console. Returns: paused, paused_at, the reason, and where a person goes to undo it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
pausedNo
paused_atNoISO 8601 time, or null.
resume_withNoWhat a person does to lift it.
paused_reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already carry readOnlyHint, idempotentHint, non-destructive, closed-world. The description adds useful context beyond that: it explains the trigger condition, the fields returned, and the out-of-band remediation path. It does not, however, discuss caching or error behavior; still strong.

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 labeled lines (Purpose, NOT for, Returns) front-load the answer. Every sentence carries distinct information: trigger, exclusion, and remediation.

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?

Output schema already documents return fields, so the description need not repeat them. It covers the very questions an agent would have: why to call, what it cannot do, and where to send a human for remediation. Fully adequate.

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?

Zero parameters, so parameter semantics is a non-issue. The description confirms the read target (this key) with no unstated inputs expected. Baseline 4 for a 0-param tool; nothing to compensate for.

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+resource: find out whether a key is stopped, since when, and the reason. Distinguishes itself from siblings by explicitly saying it is NOT for lifting the switch and pointing to why_was_this_not_sent (# send fails) as its trigger.

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?

Explicitly says when to read (a send fails with kill_switch_active) and when NOT to use it (lifting it), and clarifies that lifting requires a person in the console. No inference needed.

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