Skip to main content
Glama
flukeatzerocool

Infobroker

by flukeatzerocool
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Reload Configuration

infobroker_reload_config
Idempotent

Reload configuration from the config file to apply provider, rate-limit, and knowledge-base changes without restarting. Preserves active connections and returns a status envelope.

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 and want the changes applied immediately. Do NOT use to inspect configuration or provider state (use infobroker_inspect_providers). The tool takes no arguments: the configuration source is fixed at startup (INFOBROKER_CONFIG, merged with config.local.json), and this call simply re-reads it from disk. If the new configuration is invalid, the previous configuration stays active and an error is returned. Returns a JSON envelope prefixed [OK] or [ERROR].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

The description discloses key behaviors beyond the annotations: no restart required, active connections preserved, and rollback to previous config on invalid input. This gives the agent a clear model of side effects and safety.

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 compact and well-organized, covering purpose, usage, behavior, and output in three sentences without redundancy. Every sentence adds value.

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?

For a zero-parameter tool, the description provides all necessary context: what it does, when to invoke it, what side effects occur, and what output format to expect. No gaps remain.

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

Parameters5/5

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

The tool has zero parameters; the description explicitly notes 'takes no arguments', which is accurate and complete. Schema coverage is trivially 100%, and no additional parameter explanation is needed.

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 clearly states the tool's function with a specific verb ('re-read', 'apply') and resource ('configuration'), and distinguishes it from the sibling inspection tool by naming the alternative (infobroker_inspect_providers). No ambiguity.

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?

Explicitly states when to use (after editing config files) and when not to use (for inspection, pointing to the correct tool). Provides direct, actionable guidance.

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