Skip to main content
Glama

load_elements

Load specified plugin elements (skills, agents, commands) and return their content. Provide plugin name and element list.

Instructions

Load plugin elements (skills, agents, commands) with their content.

Args: plugin_name: Name of the plugin. request: Request body with elements to load.

Returns: Response with loaded element contents.

Raises: HTTPException: If plugin is not found or elements cannot be read.

Path Parameters:

  • plugin_name (Required): No description.

Responses:

  • 200 (Success): Successful Response

    • Content-Type: application/json

    • Response Properties:

      • plugin_name: プラグイン名

      • elements: 読み込まれた要素のリスト

    • Example:

{
  "plugin_name": "string",
  "elements": [
    "unknown_type"
  ]
}
  • 422: Validation Error

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "detail": [
    "unknown_type"
  ]
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plugin_nameYes
elementsYes読み込む要素のリスト

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
plugin_nameYesプラグイン名
elementsYes読み込まれた要素のリスト
Behavior2/5

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

No annotations provided, so the description must carry full burden. It mentions possible HTTP exceptions (plugin not found, elements cannot be read) but does not disclose side effects, permissions, or whether the operation is destructive. The response example is vague and doesn't clarify the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is structured into sections (Args, Returns, Raises, Path Parameters, Responses) which aids readability. However, it is somewhat verbose and includes redundant information (e.g., 'Path Parameters' repeats plugin_name already in input schema). The use of Japanese in descriptions may reduce clarity for English-speaking agents.

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 (2 parameters, no annotations), the description is incomplete. It does not clarify whether the tool is read-only or mutating, nor does it explain the relationship between path parameters and request body. The sibling tool list_plugins provides minimal context. The response example is vague.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% (plugin_name lacks description in schema). The description adds minimal: it mentions 'request: Request body with elements to load' but does not elaborate on plugin_name's role. The elements parameter is described in the schema (in Japanese) and the description adds little beyond that.

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 it loads plugin elements (skills, agents, commands) with their content, which is specific. It differentiates from the sibling tool list_plugins which likely only lists plugins. However, 'load' is somewhat ambiguous (could mean retrieve content or load into memory).

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 explicit guidance on when to use this tool versus alternatives. The sibling tool list_plugins is mentioned but no comparison. The description does not state prerequisites or when not to use this tool.

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/ppspps824/cc-plugin-mcp'

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