Skip to main content
Glama

activate_element

Activate a specific element by name and type to enable dynamic AI persona management within the DollhouseMCP server.

Instructions

Activate a specific element by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe element name to activate
typeYesThe element type

Implementation Reference

  • Registers all element tools including activate_element via getElementTools
    // Register element tools (new generic tools for all element types)
    this.toolRegistry.registerMany(getElementTools(instance));
  • Tool schema definition for activate_element with input validation for name and type
    tool: {
      name: "activate_element",
      description: "Activate a specific element by name",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "The element name to activate",
          },
          type: {
            type: "string",
            description: "The element type",
            enum: Object.values(ElementType),
          },
        },
        required: ["name", "type"],
      },
    },
    handler: (args: ActivateElementArgs) => server.activateElement(args.name, args.type)
  • Handler function for activate_element tool that delegates to server.activateElement(name, type)
      handler: (args: ActivateElementArgs) => server.activateElement(args.name, args.type)
    },
  • Calls getElementTools to register activate_element and other element tools to the registry
    this.toolRegistry.registerMany(getElementTools(instance));
  • ToolRegistry provides getHandler to retrieve and execute the activate_element handler during tool calls
    getHandler(name: string): ToolHandler | undefined {
      return this.tools.get(name)?.handler;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It doesn't disclose whether activation is reversible, requires permissions, affects system state, or what happens upon success/failure. 'Activate' implies a state change, but details are missing.

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 no wasted words. It directly states the tool's core function without unnecessary elaboration, making it easy to parse and understand quickly.

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?

For a tool that likely performs a state mutation (activation) with no annotations and no output schema, the description is insufficient. It doesn't explain what 'activate' entails, the outcome, error conditions, or how it differs from similar tools, leaving critical gaps for an AI agent.

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%, so parameters are well-documented in the schema. The description adds no extra meaning beyond implying 'name' identifies the element, which is already clear from the schema. Baseline 3 is appropriate as the schema handles parameter semantics adequately.

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 ('activate') and target ('a specific element by name'), which provides a basic understanding of the tool's function. However, it doesn't differentiate from sibling tools like 'deactivate_element' or explain what 'activate' means in this context, preventing a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives like 'deactivate_element' or 'get_active_elements'. The description lacks context about prerequisites, such as whether the element must exist or be in a deactivated state, leaving usage unclear.

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