Skip to main content
Glama
Sign In

Scribase

by com.scribase
OverviewDiscussionsAdmin

Get URL and keys

keys.get
Read-onlyIdempotent

The project URL and publishable (anon) key for supabase-js, as .env lines. The secret (server-only) key is included only with include_secret: true and the keys:secret scope; it bypasses row level security and must never reach client code. Scope: keys: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": "keys.get"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchNoBranch (environment) id. Optional: defaults to `production`.
project_idNoProject id. Optional: defaults to the project created or used last in this session, or the only one.
include_secretNoAlso return the secret key (needs keys:secret)
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

A4.4/5.0
Behavior5/5

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

Annotations only say this is a safe, idempotent read; the description adds the material facts an agent cannot get elsewhere: the secret key bypasses row level security, is server-only, and must never reach client code. It also discloses the returned format (.env lines) and the auth scopes for both the base and secret paths.

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?

Three sentences, front-loaded with what the tool returns before the conditional secret behavior and the security warning. Every sentence carries distinct information and nothing is repeated from the schema or annotations.

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

Completeness5/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 still specifies the return format (.env lines) and the exact condition under which the return set expands. Defaults for branch, project_id, and organization_id are covered by the schema, so nothing needed for a correct call is missing.

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?

Schema description coverage is 100%, so the schema already documents all four parameters, giving a baseline of 3. The description goes beyond the schema by tying include_secret to a concrete consequence (the secret key, its RLS bypass, and the required keys:secret scope) rather than just 'also return the secret key'.

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 precisely what is returned: the project URL and publishable (anon) key, rendered as .env lines, with the secret key as an optional extra. That is specific verb-adjacent plus resource plus format. It does not distinguish itself from near-siblings such as apikey.list or ai.keys, which keeps it short of 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 Guidelines4/5

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

It makes the condition for the optional secret key explicit (include_secret: true plus the keys:secret scope) and states the required scope keys:read for the base call, so an agent knows exactly what to request. It never names an alternative tool to use instead when only anon-key listing is needed, so there is no explicit exclusion guidance.

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