Skip to main content
Glama

Reload Configuration

infobroker_reload_config
DestructiveIdempotent

Re-read the configuration file and apply provider, rate-limit, and knowledge-base changes without restarting; active connections are preserved.

Instructions

Re-read the configuration file and apply provider, rate-limit, and knowledge-base changes without restarting; active connections are preserved. Use when you have edited config.json or config.local.json, or when passing patch to change configuration programmatically. Do NOT use to inspect configuration or provider state (use infobroker_inspect_providers). patch merges a partial config into the user layer (config.local.json) as it exists on disk, accepting only an allow-listed set of operational keys (provider enablement, priority, rate limits, timeouts and retries; response shape; the update check) and rejecting transport, credential, safety, and resource-bound keys — edit the file directly for those. It validates and activates the merged result before writing, backs up the exact bytes read, and rolls the layer back if activation fails; a null value removes that key from the layer. migrate true backs up and applies registered user-layer migrations before reloading. The call re-reads the startup configuration source and reports any user-layer schema drift. If the new configuration is invalid, the previous configuration stays active and an error is returned. Returns an [OK] or [ERROR] JSON envelope.

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": "infobroker_reload_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchNoPartial configuration merged into the user layer (config.local.json) as it exists on disk before reloading; only operational keys are accepted (provider enablement/priority/rate limits/timeouts/retries, response shape, update check), `null` removes a key, and the exact bytes read are backed up
migrateNoBack up and apply registered user-configuration-layer migrations before reloading (default false)

Output Schema

NameRequiredDescriptionDefault
metaNo
errorNo
statusYes
noticesNo
resultsNo
providerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2026.11.16
    • changedInput schema / properties / patch / description
      Previous value: -"Partial configuration deep-merged into the user layer (config.local.json) before reloading; unknown top-level keys are rejected and the previous layer is backed up"New value: +"Partial configuration merged into the user layer (config.local.json) as it exists on disk before reloading; only operational keys are accepted (provider enablement/priority/rate limits/timeouts/retries, response shape, update check), `null` removes a key, and the exact bytes read are backed up"
  2. Changed1 schema field changedv2026.10.30
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "error": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "code": {
      +          "type": "string"
      +        },
      +        "message": {
      +          "type": "string"
      +        },
      +        "remediation": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "code",
      +        "message"
      +      ],
      +      "type": "object"
      +    },
      +    "meta": {
      +      "additionalProperties": {},
      +      "properties": {},
      +      "type": "object"
      +    },
      +    "notices": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {},
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "provider": {
      +      "type": "string"
      +    },
      +    "results": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {},
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "status": {
      +      "enum": [
      +        "ok",
      +        "error"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "provider"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changedv0.1.4
    • addedInput schema / properties / patch
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Partial configuration deep-merged into the user layer (config.local.json) before reloading; unknown top-level keys are rejected and the previous layer is backed up",
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
  4. Changed1 schema field changedv0.1.3
    • addedInput schema / properties / migrate
      Added value: +{
      +  "default": false,
      +  "description": "Back up and apply registered user-configuration-layer migrations before reloading (default false)",
      +  "type": "boolean"
      +}
  5. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description goes well beyond them: it names the allow-listed key families, the rejected key families (transport, credential, safety, resource-bound), byte-level backup, activation-before-write, rollback on failure, and the fact that the previous configuration stays active on error. That is rich operational context an agent could not infer from the annotations.

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

Conciseness4/5

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

The core action and the do-not-use routing are front-loaded, and no sentence is filler. It is dense and repeats some patch details already present in the schema, which costs a point but is defensible for a destructive config-mutating tool.

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

Completeness5/5

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

Given a two-parameter mutation tool with nested patch objects, an output schema, and destructive annotations, the description covers prerequisites, failure behavior, key allow-listing, migration semantics, and error envelope format. Nothing an agent needs to invoke it safely is missing.

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 100%, so the baseline is 3; the description still adds value by explaining that patch merges into the on-disk user layer, that null removes a key, and that out-of-scope keys must be edited directly in the file. There is some overlap with the schema's own patch description, which keeps it from a 5.

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 opens with a specific verb and resource: re-read the configuration file and apply provider, rate-limit, and knowledge-base changes without restarting. It also explicitly names the sibling it is not (infobroker_inspect_providers), so an agent can distinguish it from the inspection tools without opening any schema.

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

Usage Guidelines5/5

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

It gives both when-to-use (after editing config.json or config.local.json, or when passing patch) and when-not-to-use (inspection should go to infobroker_inspect_providers). It also states the alternative for the excluded case, which is exactly what the guidance dimension asks for.

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