Skip to main content
Glama

deactivate_element

Deactivate personas, skills, templates, agents, memories, or ensembles in the DollhouseMCP server to manage AI behavioral elements.

Instructions

Deactivate a specific element

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe element name to deactivate
typeYesThe element type

Implementation Reference

  • The handler function that executes the deactivate_element tool by delegating to the server's deactivateElement method.
    handler: (args: DeactivateElementArgs) => server.deactivateElement(args.name, args.type)
  • Registration of the deactivate_element tool with description and input schema.
    tool: {
      name: "deactivate_element",
      description: "Deactivate a specific element",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "The element name to deactivate",
          },
          type: {
            type: "string",
            description: "The element type",
            enum: Object.values(ElementType),
          },
        },
        required: ["name", "type"],
      },
    },
  • TypeScript interface defining the input arguments for the deactivate_element tool.
    interface DeactivateElementArgs {
      name: string;
      type: string;
    }
  • Global registration of all element tools, including deactivate_element, to the MCP tool registry.
    this.toolRegistry.registerMany(getElementTools(instance));
  • Interface definition for the server's deactivateElement method called by the tool handler.
    deactivateElement(name: string, type: string): Promise<any>;
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Deactivate' implies a state change rather than deletion, but the description doesn't clarify whether this is reversible, what permissions are required, what happens to related data, or what the response looks like. For a mutation tool with zero annotation coverage, this is inadequate.

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 a single, efficient sentence with zero wasted words. It's appropriately sized for a simple tool and front-loads the core action without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'deactivate' entails operationally, how it differs from deletion, what the expected outcome is, or any error conditions. For a tool that likely changes system state, this leaves significant gaps.

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 description coverage is 100%, with both parameters ('name' and 'type') well-documented in the schema, including an enum for 'type'. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline of 3 for high schema coverage.

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?

The description clearly states the action ('deactivate') and target ('a specific element'), which is a specific verb+resource combination. However, it doesn't differentiate from its sibling 'activate_element' beyond the opposite action, nor does it explain what 'deactivate' means in this context compared to alternatives like 'delete_element' or 'edit_element'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'activate_element', 'delete_element', and 'edit_element', there's no indication of when deactivation is appropriate versus deletion or editing, nor any prerequisites or context for its use.

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/DollhouseMCP/DollhouseMCP'

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