agent-health

delete_liveness_subscription

Destructive

Revoke your pull subscription and its key immediately. Does not delete monitored agents. Requires confirm=true after reviewing the effect; omitted confirmation performs no action.

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": {
      "subscription_id": "<subscription_id>",
      "subscription_key": "<subscription_key>"
    },
    "name": "delete_liveness_subscription"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No
`subscription_id`	Yes
`subscription_key`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "title": "Confirm",
+  "type": "boolean"
+}

AddedOct 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so safety is partly covered. The description adds real value on top: immediate revocation behavior, explicit non-destruction of monitored agents, and the confirm guardrail defaulting to a no-op.

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?

Three tight sentences: action first, scope boundary second, guardrail third. Each sentence carries distinct information and is front-loaded, with no waste.

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 destructive tool with annotations covering the safety profile and an output schema already defined, the description supplies the remaining essentials: what is revoked, what is not affected, and the confirmation requirement.

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 0%, so the description must carry parameter meaning. It explains confirm thoroughly (required true, omitted performs no action) but leaves subscription_id and subscription_key undecorated beyond their self-evident names, so it only partially compensates for the coverage gap.

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 ('Revoke') and resource ('pull subscription and its key') and clarifies the scope boundary ('Does not delete monitored agents'), which helps separate it from delete_agent_health. It doesn't name an alternative sibling explicitly, so it falls just short of top marks.

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?

Provides invocation guidance via the confirm=true requirement and notes that omission is a no-op, which is genuinely useful. However, it never states when to prefer this tool over alternatives, and usage of the subscription flow is only implied.

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

All agent-health tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?