Skip to main content
Glama
Sign In

Scribase

by com.scribase
OverviewDiscussionsAdmin

List extensions

extensions.list
Read-onlyIdempotent

Postgres extensions this branch can enable (vector, pgmq, pg_jsonschema, index_advisor, ...) and which are on. Pass category to filter. Scope: database:read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "extensions.list"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchNoBranch (environment) id. Optional: defaults to `production`.
categoryNoOnly this category, e.g. search
project_idNoProject id. Optional: defaults to the project created or used last in this session, or the only one.
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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real value beyond them by disclosing the required permission scope (database:read) and clarifying that results include both enable-able and currently-enabled extensions. It does not mention pagination or ordering, which keeps it from a 5.

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?

A single front-loaded sentence names the resource, gives concrete example values, notes the filter, and states the auth scope. Nothing is padded and no sentence is wasted.

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?

With no output schema, the description does the necessary work of saying what comes back (available extensions and which are enabled) and what permission is needed. Only minor omissions remain, such as result ordering or whether disabled extensions are included in a category filter.

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% and each parameter (branch, category, project_id, organization_id) documents its own default behavior, so the schema carries the parameter burden. The description adds no format, allowed values, or semantics beyond restating the category filter.

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 (list) and resource (Postgres extensions) plus the two things returned: available extensions and their enabled state, with concrete examples (vector, pgmq, pg_jsonschema). It is clearly a read operation, but it never differentiates itself from the sibling extensions.enable, so it falls short of the top score.

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?

"Pass `category` to filter" is the only usage hint; there is no statement of when to prefer this tool over extensions.enable or other sibling tools, and no prerequisites are given. The implied usage (inspect what exists before enabling) is inferable but not 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