Skip to main content
Glama

Layero

by ru.layero.mcp
OverviewDiscussionsAdmin
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.

Подключить свой домен

connect_domain

Connect a custom domain to a site.

IMPORTANT: between this call and a working domain stands A PERSON. You
get DNS records — show them to the user and explain they go in at their
domain registrar. Do not wait for readiness: DNS propagates in minutes
to an hour, the platform re-checks on its own, and you check later via
`check_domain`. Spinning here burns time and context for nothing.

The address can be passed as-is: the platform reduces
`https://shop.example.com/page` to `shop.example.com` itself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe domain without scheme or slash: `example.ru` or `www.example.ru`.
projectYesThe project: its slug (`my-site`) or id, as listed by `my_projects`. The site address works too (`https://clear-garden-vypm.layero.app` or just `clear-garden-vypm`) — note that the address host is NOT always the slug.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
stateYes
checksNo
domainYes
recordsYes
workingYes
next_actionYes
next_check_hintNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"Домен без схемы и без слеша: `example.ru` или `www.example.ru`. Со схемой (`https://…`) платформа ответит отказом 422."New value: +"The domain without scheme or slash: `example.ru` or `www.example.ru`."
    • changedInput schema / properties / project / description
      Previous value: -"Проект: слаг (`my-site`) или id. Слаг — то, что видно в адресе сайта; если пользователь назвал сайт словами, возьми слаг из `my_projects`."New value: +"The project: its slug (`my-site`) or id, as listed by `my_projects`. The site address works too (`https://clear-garden-vypm.layero.app` or just `clear-garden-vypm`) — note that the address host is NOT always the slug."
  2. Changed2 schema fields changed
    • addedInput schema / properties / domain / description
      Added value: +"Домен без схемы и без слеша: `example.ru` или `www.example.ru`. Со схемой (`https://…`) платформа ответит отказом 422."
    • addedInput schema / properties / project / description
      Added value: +"Проект: слаг (`my-site`) или id. Слаг — то, что видно в адресе сайта; если пользователь назвал сайт словами, возьми слаг из `my_projects`."
  3. Added

TDQS

A5/5.0
Behavior5/5

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

Beyond the sparse openWorldHint annotation, the description discloses critical behavioral traits: the result is DNS records that require human action at a registrar, the platform re-checks asynchronously, and the input URL is normalized automatically. This gives an agent a realistic model of the tool's non-immediate, externally dependent behavior.

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 yet information-dense. The purpose is front-loaded, followed by the most critical operational warning, then a useful clarification about URL normalization. Every sentence earns its place without redundant phrasing.

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?

Given the asynchronous, human-in-the-loop nature of this operation, the description covers the essential flow: the user receives DNS records, must apply them at a registrar, and should not wait because the platform re-checks automatically. With an output schema present and only two fully covered parameters, no necessary context is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema covers both parameters, the description adds important semantics: the domain can be passed as a full URL and will be reduced to a bare host, and the project can be a slug, id, or site address with a caveat that the address host is not always the slug. This directly improves correct invocation and resolves likely confusion.

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 opens with a specific verb and resource: 'Connect a custom domain to a site.' This clearly distinguishes the operation from siblings like check_domain and list_domains. The title also reinforces the action, but the description goes beyond a tautology by stating the actual effect.

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 gives explicit behavioral guidance: show DNS records to the user, ask them to update the registrar, and do not poll for readiness. It names the follow-up tool check_domain for verifying status later and warns that spinning wastes time and context, effectively saying when not to keep waiting.

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

All Layero 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