Skip to main content
Glama

reload_hda

Reload an HDA file from disk to apply changes and expand path variables such as $JOB.

Instructions

Reload an HDA file from disk.

Args: ctx: MCP context. file_path: HDA file path; variables ($JOB) are expanded.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file_path": "<file_path>"
    },
    "name": "reload_hda"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. 'Reload from disk' implies a mutating refresh of an in-memory definition, but the description never says what is overwritten, whether unsaved in-memory edits are lost, what errors occur for a missing file, or whether permissions are required.

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?

One summary sentence followed by a short Args block; nothing is padded and the action is front-loaded. The only mild waste is the ctx: MCP context line, which adds no decision-relevant information.

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

Completeness3/5

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

For a single-parameter tool with no output schema or annotations, the definition is minimally adequate: the agent knows what to pass. It omits the consequences of reloading and any error behavior, which matters for a mutation-style operation with no annotation coverage.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it does: it identifies file_path as the HDA path and adds the non-obvious detail that variables like $JOB are expanded. The ctx entry is boilerplate but harmless. Format details such as .hda vs .otl or relative paths are not covered.

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?

States a specific verb and resource: 'Reload an HDA file from disk', which is a distinct action an agent can recognize. It does not differentiate itself from nearby siblings such as update_hda, install_hda, or reload_plugin, leaving the boundary implicit.

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?

There is no when-to-use or when-not-to-use guidance, and no prerequisites such as whether the HDA must already be installed. The agent must infer that this refreshes an existing on-disk HDA rather than creating or editing one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools