Skip to main content
Glama

reload_elements

Reload specific element types from the filesystem to update personas, skills, templates, agents, memories, or ensembles in the DollhouseMCP server.

Instructions

Reload elements of a specific type from the filesystem

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesThe element type to reload

Implementation Reference

  • The handler function for the 'reload_elements' tool. This arrow function receives the arguments and delegates to the server's reloadElements method with the provided type.
    handler: (args: ReloadElementsArgs) => server.reloadElements(args.type)
  • Input schema validation for the reload_elements tool, defining the expected 'type' parameter.
    inputSchema: {
      type: "object",
      properties: {
        type: {
          type: "string",
          description: "The element type to reload",
          enum: Object.values(ElementType),
        },
      },
      required: ["type"],
    },
  • The complete tool definition object for 'reload_elements' returned by getElementTools, which is registered to the tool registry.
    {
      tool: {
        name: "reload_elements",
        description: "Reload elements of a specific type from the filesystem",
        inputSchema: {
          type: "object",
          properties: {
            type: {
              type: "string",
              description: "The element type to reload",
              enum: Object.values(ElementType),
            },
          },
          required: ["type"],
        },
      },
      handler: (args: ReloadElementsArgs) => server.reloadElements(args.type)
    },
  • Registration of all element tools (including reload_elements) to the ToolRegistry during server setup.
    this.toolRegistry.registerMany(getElementTools(instance));
  • Type definition for the underlying server.reloadElements method called by the tool handler.
    reloadElements(type: string): Promise<any>;
Behavior2/5

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

With no annotations, the description carries the full burden but only states the action without behavioral details. It doesn't disclose if this is a read-only operation, if it affects system state, requires permissions, has side effects like clearing caches, or handles errors, leaving significant gaps for a mutation-like tool.

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 that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it highly concise and well-structured.

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 no annotations and no output schema, the description is incomplete for a tool that likely mutates system state by reloading from filesystem. It lacks details on behavior, outcomes, error handling, or how it interacts with other tools, failing to compensate for the missing structured data.

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 the schema fully documents the single parameter 'type' with its enum values. The description adds no additional meaning beyond implying the parameter specifies what to reload, aligning with the baseline 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 verb ('reload') and resource ('elements of a specific type from the filesystem'), making the purpose understandable. However, it doesn't differentiate from siblings like 'sync_portfolio' or 'get_collection_cache_health' that might involve similar filesystem operations, keeping it from 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. For example, it doesn't mention if this is for refreshing cached data, recovering from errors, or when changes are made externally, nor does it reference siblings like 'sync_portfolio' or 'get_collection_cache_health' for context.

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