Skip to main content
Glama

t2000_lock

Freeze all agent operations immediately as an emergency stop. Only a human can unlock via terminal command.

Instructions

Freeze all agent operations immediately. Only a human can unlock via t2000 unlock in the terminal. Use this as an emergency stop.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The registration and handler implementation of the 't2000_lock' tool, which calls 'agent.enforcer.lock()' to freeze operations.
    server.tool(
      't2000_lock',
      'Freeze all agent operations immediately. Only a human can unlock via `t2000 unlock` in the terminal. Use this as an emergency stop.',
      {},
      async () => {
        try {
          agent.enforcer.lock();
          return {
            content: [{
              type: 'text',
              text: JSON.stringify({
                locked: true,
                message: 'Agent locked. Only a human can unlock via: t2000 unlock',
              }),
            }],
          };
        } catch (err) {
          return errorResult(err);
        }
      },
    );
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses critical behavioral traits: the tool is destructive (freezes operations), requires human intervention to reverse, and is intended for emergencies. However, it doesn't specify side effects like data persistence or system state changes.

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?

The description is front-loaded with the core action, followed by critical constraints and usage context in just two sentences. Every sentence adds essential information with zero waste.

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?

Given the tool's high-stakes nature (emergency stop) and lack of annotations/output schema, the description is mostly complete. It covers purpose, usage, and key behavioral constraints, though it could mention potential risks or confirmation steps.

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?

There are 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose and usage.

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 clearly states the specific action ('Freeze all agent operations immediately') and resource ('agent operations'), distinguishing it from sibling tools that handle financial transactions, configuration, or monitoring. It uses precise verbs and identifies the scope of impact.

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 explicitly states when to use this tool ('as an emergency stop') and provides a clear alternative for reversal ('Only a human can unlock via `t2000 unlock` in the terminal'), distinguishing it from other tools that perform routine operations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mission69b/t2000'

If you have feedback or need assistance with the MCP directory API, please join our Discord server