Skip to main content
Glama

Set public access

set_database_public_access
Idempotent

Opens the database to the internet at its public host and port (IPv4 and IPv6, TLS and password still required), or closes it. sources restricts who may connect (IPv4/IPv6 addresses or ranges); omitted it is left as is, null or [] means everyone. Prefer listing the user's addresses. Live within about 30 seconds. Scope: network.write.

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": {
      "database": "<database>",
      "enabled": "<enabled>"
    },
    "name": "set_database_public_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYestrue opens the database to the internet; false closes it, leaving the private network only.
sourcesNoIPv4/IPv6 addresses or ranges allowed to connect from the internet, up to 50. Omitted: left as is; null or []: everyone.
databaseYesDatabase id, as returned by list_databases or create_database.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / enabled / description
      Added value: +"true opens the database to the internet; false closes it, leaving the private network only."
    • addedInput schema / properties / sources / description
      Added value: +"IPv4/IPv6 addresses or ranges allowed to connect from the internet, up to 50. Omitted: left as is; null or []: everyone."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare a non-read-only, open-world, idempotent, non-destructive write, and the description adds real context beyond them: authentication is still enforced, changes propagate in about 30 seconds, and the scope is network.write. It stops short of describing failure modes or whether existing connections are dropped.

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?

Three tight sentences, front-loaded with the state change, then the sources semantics, then the timing and scope note. The sources clause duplicates the schema wording slightly, which is the only wasted space.

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 three-parameter mutation with no output schema, the description covers the security caveat, propagation delay, and permission scope. Missing only edge-case behavior, such as how invalid or private-range addresses in sources are handled.

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 all three parameters are already documented, and the description's explanation of sources (omitted = unchanged, null/[] = everyone) largely restates the schema. The added value is limited to the allowlist preference hint, which justifies the baseline 3 rather than more.

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?

States a specific verb and resource — opening or closing a database to the internet at its public host and port — and immediately scopes what that does and does not mean (IPv4/IPv6, TLS and password still required). An agent can distinguish this from user-level access tools without opening the schema.

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?

Provides one concrete usage preference ('Prefer listing the user's addresses') for the sources parameter, which implies a default posture toward allowlisting. However, it never says when to use this versus alternatives such as set_database_user_access or firewall rules, so routing guidance is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.