Skip to main content
Glama
Sign In
Baasix MCP Server

Baasix MCP Server

by tspvivek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

baasix_update_settings

Update your Baasix application settings by submitting a settings object to modify configuration.

Instructions

Update application settings

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": {
      "settings": "<settings>"
    },
    "name": "baasix_update_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
settingsYesSettings object to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It communicates mutation ('update') but does not state permission requirements, whether the update is partial or full replacement, persistence effects, or side effects on the application.

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?

At three words, the description contains zero filler and is front-loaded with the verb. It is concise, though the brevity sacrifices useful detail that the other dimensions penalize.

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?

With no annotations, no output schema, and a nested-object parameter, the one-line description leaves out essential context: the expected shape of the settings object, how the update behaves, return values, and any permission requirements. An agent could not confidently invoke this tool for a non-trivial settings change.

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 description coverage is 100% since the sole parameter 'settings' has a description, so the baseline is 3. The description adds only the 'application' context and does not specify accepted keys, nested structure, or update semantics beyond what the schema already states.

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?

The description uses the verb 'update' with the resource 'application settings', making the core operation clear. It also distinguishes this tool from siblings like baasix_get_settings and other update_* tools, though it does not elaborate on which settings are included.

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 guidance on when to use this tool, what prerequisites exist, or how it compares to alternatives like baasix_get_settings for reading settings. The description is a bare one-liner with no usage context.

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