Skip to main content
Glama
Sign In

Scribase

by com.scribase
OverviewDiscussionsAdmin

Enable an extension

extensions.enable

Enable an allowlisted Postgres extension on a branch. With name vector and search_table: true it also creates a semantic search table and match function. Scope: database: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": {
      "name": "<name>"
    },
    "name": "extensions.enable"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesExtension name, e.g. vector
tableNoSearch table name (with search_table)
branchNoBranch (environment) id. Optional: defaults to `production`.
schemaNoSchema to install it in. Optional.
dimensionsNoEmbedding dimensions (with search_table)
project_idNoProject id. Optional: defaults to the project created or used last in this session, or the only one.
search_tableNoWith vector: also create the semantic search table
organization_idNoOrganization id. Optional: defaults to the token's organization, or the only one you belong to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that only allowlisted extensions are accepted and that enabling vector with search_table:true creates a search table and match function — a side effect the destructiveHint=false / idempotentHint=false flags alone would not reveal. It does not say what happens when the extension is already enabled, which matters given idempotentHint=false.

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, front-loaded with the core action, then the conditional side effect, then the scope requirement. No redundant restatement of the title or schema.

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 an 8-parameter mutation with full schema coverage and no output schema, the description covers the action, the allowlist constraint, the main side effect, and the required scope. It leaves out failure behavior on already-enabled extensions and what enabling returns, a minor gap.

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 the baseline is 3. The description does add cross-parameter semantics by tying name=vector to search_table:true (and implicitly table/dimensions), but it says nothing about the branch, schema, project_id, or organization_id defaults beyond what the schema already documents.

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?

States a specific verb and resource ('Enable an allowlisted Postgres extension on a branch') plus the vector/search_table special case, so the action is unambiguous. It does not explicitly name the sibling extensions.list as the discovery counterpart, which keeps it from a 5.

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 word 'allowlisted' implies a precondition and the vector/search_table sentence shows one concrete usage scenario, but there is no explicit when-to-use vs. when-not guidance or pointer to extensions.list for discovery. Usage is implied rather than stated.

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

All Scribase toolsInspect
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.

Resources