Layero

This connector has been deprecated

Duplicate listing of the same server under an old namespace. The maintained listing is Layero (ru.layero/layero): same endpoint https://mcp.layero.ru/mcp, current description and tools. The landing-page generator described here was removed in MCP 2.0.

Data API базы: состояние

data_api_status

Read-only

Whether the database has the Data API enabled, its address, keys and the sites allowed to call it.

Keys are shown by prefix; the public key also comes with its value (it is
not a secret: it ships in the site bundle). Secret keys are never returned
or stored. Enabling the API goes through the CLI; as in
Supabase, new tables in `public` are then open to the roles and RLS
decides the rows, so every table needs RLS on. Sign-in and files are
enabled only by the person in the dashboard.

Input Schema

Name	Required	Description	Default
`database`	No	The database: name, slug or id. Without it — the organization's only database with the Data API enabled.
`organization`	No	Organization slug. Without it — the only one, or the personal one.

Output Schema

Name	Required	Description	Default
`url`	No
`keys`	No
`sites`	No
`enabled`	Yes
`database`	Yes
`url_note`	No
`next_action`	Yes
`auth_enabled`	No
`organization`	Yes
`files_enabled`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / url_note

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Url Note"
+}

Changed2 schema fields changedOct 26, 2026

addedOutput schema / properties / auth_enabled

Added value: +{
+  "default": false,
+  "title": "Auth Enabled",
+  "type": "boolean"
+}

addedOutput schema / properties / files_enabled

Added value: +{
+  "default": false,
+  "title": "Files Enabled",
+  "type": "boolean"
+}

Changed2 schema fields changedSep 18, 2026

changedInput schema / properties / database / description

Previous value: -"База: имя, слаг или id. Без него — единственная база организации с включённым Data API."New value: +"The database: name, slug or id. Without it — the organization's only database with the Data API enabled."

changedInput schema / properties / organization / description

Previous value: -"Организация (слаг). Без него — единственная или личная."New value: +"Organization slug. Without it — the only one, or the personal one."

AddedSep 14, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Beyond readOnlyHint=true, the description discloses real behavioral detail: keys are returned by prefix, the public key value is included because it is not secret, and secret keys are never returned or stored. It also warns that new public tables become role-accessible so RLS must be on, which is meaningful side-effect context the annotations do not cover.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in sentence one, but the trailing material drifts into general Supabase semantics about RLS and dashboard toggles that reads more like security advice than invocation guidance. The statement is informative yet partly padded for a two-optional-parameter read tool.

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?

An output schema exists, so return values need not be spelled out, and the description usefully previews the key-masking convention so the agent can interpret the response. Combined with 100% schema coverage and a readOnly annotation, this is sufficient to call the tool correctly.

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 both the `database` and `organization` parameters already document their 'omit for the only/personal one' defaulting behavior in the schema itself. The description adds nothing about resolution order or ambiguity handling, so the baseline 3 applies.

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?

The opening sentence names a specific resource and enumerates what is reported (enabled flag, address, keys, allowed sites), so an agent knows this is a read-only status probe. It never distinguishes itself from siblings like data_api_keys, data_api_origins or data_api_probe, which appear to surface overlapping slices of the same state, so sibling differentiation is missing.

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?

There is no explicit 'use this when' or named alternative, but the notes that enabling goes through the CLI and that sign-in/files are turned on in the dashboard implicitly bound the tool's scope to inspection only. The agent must still infer whether to call this versus data_api_keys or data_api_origins.

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

All Layero tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?