Skip to main content
Glama
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_grant
Destructive

Who may call a method of a table or a function: shows the SQL and applies it after consent.

OPENS DATA TO THE INTERNET. Call it without `apply` first: the platform
returns the commands and warnings (for example "row-level security is
off — a visitor will get every row"). Show them to the person. With
apply=true a client with forms asks the person itself; without forms get
consent in the chat and pass confirmed=true together with expected_sql
from the preview.

Methods you do not name keep their current level. Exactly the shown
commands are applied: if the grants changed meanwhile, the platform
refuses — show the new ones. Needs a token with the admin scope, for the
preview too.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
getNoReading the table. closed — nobody; visitor — any site visitor; user — people signed in to the app; server — only a server holding the secret key.
callNoCalling the function. closed — nobody; visitor — any site visitor; user — people signed in to the app; server — only a server holding the secret key.
postNoInserting rows into the table. Same levels as `get`.
applyNofalse (default) — only show the commands. true — apply them after the person's consent.
patchNoUpdating rows of the table. Same levels as `get`.
deleteNoDeleting rows of the table. Same levels as `get`.
objectYesA table `schema.name` or a function `schema.name`; for an overloaded function — `schema.name(types)`. As listed by data_api_methods.
databaseNoThe database: name, slug or id. Without it — the organization's only database with the Data API enabled.
confirmedNotrue — the person has already agreed in the chat after seeing what will change. A client with forms does not need it: the server asks the person itself. Never set it without the person's explicit consent.
expected_sqlNoThe `sql` commands from the preview answer that the person saw. Required with confirmed=true: only these are applied.
organizationNoOrganization slug. Without it — the only one, or the personal one.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sqlYes
nextYes
objectYes
appliedYes
currentYes
databaseYes
warningsNo
next_actionYes
organizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedInput schema / properties / apply / description
      Previous value: -"false (по умолчанию) — только показать команды. true — применить после согласия человека."New value: +"false (default) — only show the commands. true — apply them after the person's consent."
    • changedInput schema / properties / call / description
      Previous value: -"Вызов функции. closed — закрыто; visitor — любой посетитель сайта; user — вошедшие в приложение; server — только сервер с секретным ключом."New value: +"Calling the function. closed — nobody; visitor — any site visitor; user — people signed in to the app; server — only a server holding the secret key."
    • changedInput schema / properties / confirmed / description
      Previous value: -"true — человек уже согласился в чате, увидев, что поменяется. Клиенту с формами не нужен: он спросит сам. Без явного согласия человека не ставь."New value: +"true — the person has already agreed in the chat after seeing what will change. A client with forms does not need it: the server asks the person itself. Never set it without the person's explicit consent."
    • 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 / delete / description
      Previous value: -"Удаление строк таблицы."New value: +"Deleting rows of the table. Same levels as `get`."
    • changedInput schema / properties / expected_sql / description
      Previous value: -"Команды `sql` из ответа показа, которые видел человек. Обязательны с confirmed=true: применятся только они."New value: +"The `sql` commands from the preview answer that the person saw. Required with confirmed=true: only these are applied."
    • changedInput schema / properties / get / description
      Previous value: -"Чтение таблицы. closed — закрыто; visitor — любой посетитель сайта; user — вошедшие в приложение; server — только сервер с секретным ключом."New value: +"Reading the table. closed — nobody; visitor — any site visitor; user — people signed in to the app; server — only a server holding the secret key."
    • changedInput schema / properties / object / description
      Previous value: -"Таблица `схема.имя` или функция `схема.имя`, при перегрузке — `схема.имя(типы)`. Как в data_api_methods."New value: +"A table `schema.name` or a function `schema.name`; for an overloaded function — `schema.name(types)`. As listed by data_api_methods."
    • changedInput schema / properties / organization / description
      Previous value: -"Организация (слаг). Без него — единственная или личная."New value: +"Organization slug. Without it — the only one, or the personal one."
    • changedInput schema / properties / patch / description
      Previous value: -"Изменение строк таблицы."New value: +"Updating rows of the table. Same levels as `get`."
    • changedInput schema / properties / post / description
      Previous value: -"Добавление строк в таблицу."New value: +"Inserting rows into the table. Same levels as `get`."
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations indicate openWorld and destructive, and the description reinforces with 'OPENS DATA TO THE INTERNET', mentions row-level security warnings, exact command matching and refusal if grants changed. It adds significant context beyond annotations, including admin token requirement for preview.

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?

The description is a few paragraphs, front-loads purpose, then provides sequential usage steps and warnings. It is efficient and well-structured, though slightly verbose in places; every sentence contributes to usage or behavior.

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?

Given 11 parameters, output schema, and complexity, the description covers the core workflow (preview→apply), consent handling, and key warnings. It doesn't detail every parameter but schema handles that. It is complete for an agent to safely use the tool.

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 covers all parameters with descriptions (100%), so baseline is 3. The description adds semantic context for confirmed and expected_sql, linking them to the preview step and explaining when they are required. It enriches param understanding without redundancy.

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 description states the tool grants access to a table or function method, showing SQL and applying after consent. It is specific about the resource (method of table/function) and distinguishes it from listing tools like data_api_methods, though it could more explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Provides explicit step-by-step guidance: call without apply first to preview, then apply with consent (through forms or chat), pass confirmed=true with expected_sql. It warns about grants changing and refusal, and states admin scope requirement. This is clear when-to-use and when-not-to-use guidance.

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.

Resources