Skip to main content
Glama
Sign In
openclaw-control-mcp

openclaw-control-mcp

by smurfy92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

openclaw_secrets_reload

Apply secret file changes by reloading the gateway's secret store from disk, avoiding a restart.

Instructions

Reload the gateway's secret store from disk. Wraps secrets.reload. Use after editing the secrets file out-of-band so the gateway picks up new values without a restart.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "openclaw_secrets_reload"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceNoOptional OpenClaw instance to route this call to (e.g. 'default', 'work'). Falls back to the active default instance, or the OPENCLAW_GATEWAY_URL/TOKEN env vars when set. List configured instances with openclaw_setup_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must convey safety and side effects. It mentions wrapping an internal function and the purpose but omits potential failure modes or permissions 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?

The description is extremely concise with two sentences, no redundant information, and the primary action stated first.

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

Completeness4/5

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

Given the simplicity of the operation and no output schema, the description covers the essential information. It could mention what happens on failure, but it is sufficiently complete for the tool's purpose.

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 coverage is 100%, and the schema includes a detailed description for the only parameter. The tool description does not add further value beyond what the schema already provides.

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

Purpose5/5

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

The description uses a specific verb ('Reload') and resource ('gateway's secret store from disk'), clearly distinguishing it from sibling tools like openclaw_secrets_set or openclaw_secrets_resolve.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use ('after editing the secrets file out-of-band') and the benefit ('picks up new values without a restart'). No alternatives are mentioned, but the use case is narrow.

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