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_probe

A real request to a method through the gateway — as a visitor, a user or the server.

The platform supplies the key and the token. Writes (POST, PATCH, DELETE,
a function call) are rolled back: rows in the database do not change,
but the rollback does not undo sequence numbers, calls from the database
to the outside, session locks or the daily call quota. The answer is
real: grants, row policies and refusals are the same the site will see.
Needs a token with the admin scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoBody for POST and PATCH.
pathYesPath from the database address: `/rest/v1/products`, `/rest/v1/rpc/order_create` or `/whoami` (GET only).
roleNoOn whose behalf: visitor — a visitor with the public key, user — a signed-in user (needs user_id), server — the secret key.visitor
queryNoQuery parameters, PostgREST style: {"select": "id,title", "price": "gt.100"}.
methodYesHTTP method.
schemaNoThe table's schema: api, public or app. Without it the name is looked up in the order api → public → app — pass it when tables with the same name exist in several schemas. Not needed for functions and /whoami.
user_idNoFor role=user: id of the app user.
databaseNoThe database: name, slug or id. Without it — the organization's only database with the Data API enabled.
organizationNoOrganization slug. Without it — the only one, or the personal one.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNo
rowsNo
totalNo
callerNo
statusNo
requestYes
databaseYes
elapsed_msNo
next_actionYes
owner_totalNo
rolled_backNo
organizationYes
body_shortenedNo
body_truncatedNo
rollback_expectedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / body / description
      Previous value: -"Тело для POST и PATCH."New value: +"Body for POST and PATCH."
    • 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 / method / description
      Previous value: -"HTTP-метод."New value: +"HTTP method."
    • changedInput schema / properties / organization / description
      Previous value: -"Организация (слаг). Без него — единственная или личная."New value: +"Organization slug. Without it — the only one, or the personal one."
    • changedInput schema / properties / path / description
      Previous value: -"Путь от адреса базы: `/rest/v1/products`, `/rest/v1/rpc/order_create` или `/whoami` (только GET)."New value: +"Path from the database address: `/rest/v1/products`, `/rest/v1/rpc/order_create` or `/whoami` (GET only)."
    • changedInput schema / properties / query / description
      Previous value: -"Параметры запроса как у PostgREST: {\"select\": \"id,title\", \"price\": \"gt.100\"}."New value: +"Query parameters, PostgREST style: {\"select\": \"id,title\", \"price\": \"gt.100\"}."
    • changedInput schema / properties / role / description
      Previous value: -"От чьего имени: visitor — посетитель с публичным ключом, user — вошедший пользователь (нужен user_id), server — секретный ключ."New value: +"On whose behalf: visitor — a visitor with the public key, user — a signed-in user (needs user_id), server — the secret key."
    • changedInput schema / properties / schema / description
      Previous value: -"Схема таблицы: api, public или app. Без неё имя ищется по порядку api → public → app — указывай, когда одноимённые таблицы есть в нескольких схемах. Функциям и /whoami не нужна."New value: +"The table's schema: api, public or app. Without it the name is looked up in the order api → public → app — pass it when tables with the same name exist in several schemas. Not needed for functions and /whoami."
    • changedInput schema / properties / user_id / description
      Previous value: -"Для role=user: id пользователя приложения."New value: +"For role=user: id of the app user."
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations indicate openWorldHint=true and destructiveHint=false, and the description adds substantial behavioral context: writes are rolled back, but sequence numbers, external calls, session locks, and quota are not rolled back; answer is real; needs admin scoped token. This goes beyond the annotations significantly. Minor gap: no mention of rate limits or errors, but the rollback caveat is valuable.

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?

The description is compact, front-loaded with the core purpose, and every sentence contributes: purpose, rollback caveats, realness of response, and auth requirement. No fluff; structured logically.

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 9 optional parameters, output schema presence, and annotations, the description covers purpose, safety, auth, and key side effects. It could mention what the response contains (real response body), but output schema existence and the statement 'The answer is real' suffice. Small gap: no mention of idempotency or concurrency, but not necessary for a probe 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 description coverage is 100%, so baseline is 3. The description adds meaning by clarifying role semantics ('visitor — a visitor with the public key', 'user — a signed-in user (needs user_id)', 'server — the secret key') and schema resolution order ('api → public → app'). This exceeds schema-provided descriptions and helps the agent use parameters correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('probe' / 'A real request to a method through the gateway') and a specific resource (Data API method via gateway). It distinguishes from siblings like data_api_grant, data_api_keys, data_api_methods by emphasizing execution and real response with rollback. Clear and actionable.

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?

The description explains when to use it: for a real request with real grants, row policies, refusals; clarifies that writes are rolled back but side effects remain; notes admin scope token requirement. It contrasts with sibling tools implicitly by focusing on probing a method vs managing keys/grants. This is explicit enough for an agent to select correctly.

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