BorealHost

manage_db_user

Manage a database user on a site.

Actions: "create" (user+password), "drop" (user), "set_password" (user+password), "grants" (list a user's grants), "grant" / "revoke" (user+database, optional privileges e.g. "ALL" or "SELECT,INSERT").

Requires: API key with write scope.

Returns: {"engine", "action", "result": {...}}

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": {
      "slug": "<slug>",
      "action": "<action>"
    },
    "name": "manage_db_user"
  }
}

Input Schema

Name	Required	Default
`host`	No
`slug`	Yes
`user`	No
`action`	Yes
`engine`	No	mysql
`database`	No
`password`	No
`privileges`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedAug 5, 2026

TDQS

A4/5.0

Behavior3/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. It discloses the permission requirement (write scope) and the return shape, and lists actions including destructive 'drop'. However, it does not explicitly warn about irreversibility or side effects, and lacks detail on how actions affect the database.

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 well-structured: a lead sentence, a bulleted action list, a one-line requirement, and a return format. Every sentence adds value, with no redundant or promotional language.

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

Completeness4/5

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

For a tool with eight parameters and multiple sub-actions, the description covers key behaviors, parameter mappings, return format, and permission needs. It lacks default values for host/engine and exact action enum formatting, but is sufficient for an agent to correctly select and invoke the tool.

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?

The input schema has 0% description coverage, so the description must compensate. It does so by mapping actions to parameters (e.g., create requires user+password; grant/revoke require user+database+privileges) and providing privilege examples. However, not all parameters (slug, host, engine) are explained, leaving some ambiguity.

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 specifies the tool manages a database user and enumerates concrete actions (create, drop, set_password, grants, grant, revoke). It distinguishes from sibling tools like list_db_users (read-only listing) and execute_query (SQL queries).

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

Usage Guidelines3/5

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

The description lists actions and parameter requirements, implying when to use the tool (for database user management). However, it does not explicitly name alternatives or exclusions, such as 'use list_db_users for listing users' or 'use execute_query for raw SQL'. The write-scope requirement is stated, but alternative guidance is absent.

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

All BorealHost tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.