Skip to main content
Glama

Update Server Configuration

update_configuration

Updates active MCP server settings—instruction level, tool filters, and briefing preferences—without restarting, so AI sessions keep persistent project context.

Instructions

Dynamically update the MCP server configuration (instruction level, tool filters, briefing preferences) without restarting the server.

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

Input Schema

NameRequiredDescriptionDefault
tool_filterNoA comma-separated list of tool groups to enable, or "all"
briefing_prsNo
project_numberNo
briefing_issuesNo
briefing_copilotNo
briefing_entriesNo
briefing_pr_statusNo
briefing_summariesNo
briefing_workflowsNo
briefing_milestonesNo
briefing_include_teamNo
briefing_workflow_statusNo

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
detailsNoAdditional error context
successYes
updatedYes
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed21 schema fields changedv9.1.0
    • removedInput schema / properties / briefing_entries / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / briefing_entries / minimum
      Removed value: -0
    • changedInput schema / properties / briefing_entries / type
      Previous value: -"integer"New value: +[
      +  "number",
      +  "string"
      +]
    • removedInput schema / properties / briefing_issues / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / briefing_issues / minimum
      Removed value: -0
    • changedInput schema / properties / briefing_issues / type
      Previous value: -"integer"New value: +[
      +  "number",
      +  "string"
      +]
    • removedInput schema / properties / briefing_milestones / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / briefing_milestones / minimum
      Removed value: -0
    • changedInput schema / properties / briefing_milestones / type
      Previous value: -"integer"New value: +[
      +  "number",
      +  "string"
      +]
    • removedInput schema / properties / briefing_prs / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / briefing_prs / minimum
      Removed value: -0
    • changedInput schema / properties / briefing_prs / type
      Previous value: -"integer"New value: +[
      +  "number",
      +  "string"
      +]
    • removedInput schema / properties / briefing_summaries / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / briefing_summaries / minimum
      Removed value: -0
    • changedInput schema / properties / briefing_summaries / type
      Previous value: -"integer"New value: +[
      +  "number",
      +  "string"
      +]
    • removedInput schema / properties / briefing_workflows / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / briefing_workflows / minimum
      Removed value: -0
    • changedInput schema / properties / briefing_workflows / type
      Previous value: -"integer"New value: +[
      +  "number",
      +  "string"
      +]
    • removedInput schema / properties / project_number / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / project_number / minimum
      Removed value: --9007199254740991
    • changedInput schema / properties / project_number / type
      Previous value: -"integer"New value: +[
      +  "number",
      +  "string"
      +]
  2. First observedv9.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the mutation profile is largely covered. The description adds real value with the dynamic-application trait ('without restarting the server'). However, it omits critical behavioral questions for an update tool: whether omitted keys are preserved or reset, whether changes persist across restarts, and what validation/rejection looks like. No contradiction with 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?

A single front-loaded sentence with no filler, and the effect clause ('without restarting the server') is placed where it reads immediately. The parenthetical is the only weak spot because one of its three items ('instruction level') does not map to a real parameter, making that slot non-earning.

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?

Twelve parameters at 8% schema coverage with no required fields and an output schema present means the description must carry the parameter and merge-semantics load — and it does not. An agent cannot determine what each briefing_* key controls, whether passing a subset resets the rest, or how tool_filter interacts with currently active groups. For a live server mutation this is a significant gap despite returns being covered by the output schema.

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 description coverage is 8% — only tool_filter is documented, and the other 11 parameters (briefing_prs, briefing_issues, briefing_summaries, briefing_entries, project_number, etc.) have no descriptions at all. The description only names broad categories and never explains that briefing_* are counts/sizes, nor why briefing_pr_status is boolean while briefing_prs is number-or-string. It also references 'instruction level', which is not a schema property at all, so the reader cannot map categories to actual keys.

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?

Names a specific verb and resource ("update the MCP server configuration") plus the scope of what is configurable (instruction level, tool filters, briefing preferences) and the key effect (no restart). An agent can tell this is runtime config mutation rather than content mutation, which separates it from update_entry/update_project/team_update_entry. Loses a point because 'instruction level' does not correspond to any parameter in the schema, muddying exactly what is being configured.

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 guidance, no statement of prerequisites (e.g. does this need admin scope?), and no pointer to any alternative for changing tool availability. The only implicit cue is 'without restarting the server', which hints at live tuning but does not tell the agent under which conditions to call this versus other tools.

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