Skip to main content
Glama
Sign In
ArcadeDB Multi-Model DBMS

ArcadeDB Multi-Model DBMS

Official
by ArcadeData
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

set_server_setting

Update a server configuration setting at runtime. Changes take effect immediately but may not persist across restarts; check available settings with get_server_settings first.

Instructions

Update a server configuration setting at runtime. Changes take effect immediately but may not persist across server restarts (depends on the setting). Use get_server_settings first to see available settings and their current values.

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": {
      "key": "<key>",
      "value": "<value>"
    },
    "name": "set_server_setting"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe configuration key (e.g., 'arcadedb.maxPageRAM', 'arcadedb.asyncWorkerThreads').
valueYesThe new value for the setting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, description discloses key behavioral traits: changes take effect immediately, may not persist across restarts. This goes beyond the schema and provides useful runtime behavior context.

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?

Two sentences, no filler. First sentence states action and effects; second sentence provides a usage tip. Well-structured and efficient.

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?

Adequate for a simple two-parameter tool with no output schema. Mentions persistence behavior but does not cover error conditions or authorization needs. Could be more complete.

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%, so baseline is 3. Description gives example key values but does not add significant meaning beyond the schema.

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?

Clearly states 'Update a server configuration setting at runtime', which is a specific verb (update) and resource (server configuration setting). Distinguishes from sibling get_server_settings which is for reading.

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?

Explicitly advises 'Use get_server_settings first to see available settings and their current values', providing a clear prerequisite. Does not specify when not to use, but the guidance is adequate.

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