Skip to main content
Glama

get_element_details

Retrieve detailed information about personas, skills, templates, agents, memories, or ensembles in the DollhouseMCP server for dynamic AI persona management.

Instructions

Get detailed information about a specific element

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe element name to get details for
typeYesThe element type

Implementation Reference

  • The MCP tool handler for get_element_details. Receives arguments and delegates to the server's getElementDetails method.
    handler: (args: GetElementDetailsArgs) => server.getElementDetails(args.name, args.type)
  • Input schema validation for the get_element_details tool defining name and type parameters.
    inputSchema: {
      type: "object",
      properties: {
        name: {
          type: "string",
          description: "The element name to get details for",
        },
        type: {
          type: "string",
          description: "The element type",
          enum: Object.values(ElementType),
        },
      },
      required: ["name", "type"],
    },
  • TypeScript interface defining the arguments for get_element_details.
    interface GetElementDetailsArgs {
      name: string;
      type: string;
    }
  • Registration of element tools including get_element_details via getElementTools call.
    this.toolRegistry.registerMany(getElementTools(instance));
  • Interface definition of the underlying server.getElementDetails method in IToolHandler.
    getElementDetails(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. The description only states it 'gets detailed information' without specifying what that information includes, whether it's read-only (implied but not stated), what permissions are required, or how errors are handled. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 gets straight to the point with zero wasted words. It's appropriately sized for a simple retrieval tool and front-loads the core purpose 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 tool has no annotations, no output schema, and operates in a complex ecosystem with many sibling tools, the description is insufficiently complete. It doesn't explain what constitutes 'detailed information', how this differs from other element-related tools, or what the expected return format might be. For a tool in this context, more completeness is needed.

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 already fully documents both parameters (name and type with enum values). The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain what 'element' means in context or provide examples. With complete schema coverage, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose as 'Get detailed information about a specific element', which is clear but vague. It specifies the verb ('Get') and resource ('element'), but doesn't differentiate from siblings like 'get_element_relationships' or 'list_elements'. The description is adequate but lacks specificity about what 'detailed information' entails.

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 'get_element_relationships', 'list_elements', and 'search_all', there's no indication of when this specific detail-retrieval tool is appropriate versus other query tools. The description offers no context about use cases or exclusions.

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