Skip to main content
Glama

Resume AI autonomy

resume_ai_autonomy
Destructive

Resume autonomous AI actions (the twin of ankra ai autonomy resume): restores exactly what the pause turned off - the remediation policy and the agents named in the pause record - and reports any agent that no longer exists. An agent someone disabled deliberately stays disabled. Refused when nothing is paused. Requires ai.manage and a credential that reaches the whole organisation (one held to a project is refused), and over a token one whose scopes name ai_actions.approve (mcp:write alone is refused, as for decide_pending_action). In chat it always raises a confirmation card, whatever the session's autonomy: a person's yes lifts the pause. The answer's autonomy.paused_through is null because nothing is paused any more.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag this as destructive and non-idempotent; the description adds far more than they do - exact restore semantics, reporting of vanished agents, preservation of deliberate disables, refusal when nothing is paused, authorization and credential constraints, mandatory chat confirmation card, and the post-state of autonomy.paused_through. No contradiction with the destructiveHint=true annotation.

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?

It is dense and front-loaded with the core action first, but a few parenthetical asides ('the twin of `ankra ai autonomy resume`', the repeated token-scope caveats referencing decide_pending_action) add length without much selection value.

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 zero-parameter mutation with no output schema, the description covers authorization, side effects, edge cases, confirmation behavior, and the relevant output field, leaving nothing an agent needs to know before calling it.

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 of 4 applies; the description adds no parameter detail because none is needed, and the schema is fully documented.

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?

The description opens with a specific verb and resource ('Resume autonomous AI actions'), scopes it precisely ('restores exactly what the pause turned off - the remediation policy and the agents named in the pause record'), and implicitly distinguishes it from pause_ai_autonomy by describing the inverse operation.

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?

It states the triggering condition (something must be paused, otherwise 'Refused when nothing is paused'), the boundary case ('An agent someone disabled deliberately stays disabled'), and the requirement context (ai.manage, org-wide credential, ai_actions.approve scope over a token). An agent knows both when this applies and when it will be rejected.

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.