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.

Мои сайты

my_projects

Read-onlyIdempotent

The user's sites on Layero.

Thirty most recent by default. The full list is rarely needed, while
flooding half your context with it is easy: an active user has dozens
of projects.

`url` is the canonical (production) address. `repo`, `branch` and
`root_directory` say where the project is built from: all three are
null for a project without a repository (CLI or `publish_site`);
`root_directory` is the app folder inside a monorepo, null for the
repository root.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`repo`	No	Only projects built from this repository: `owner/repo` (case-insensitive; a full repository URL works too). Use it to see whether a repository is already linked and from which folders. `limit` applies after the filter.
`limit`	No	How many of the most recent projects to return. The default of 30 is almost always enough; raise it (up to 100) only when the user is looking for an old site that is not in the list.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 19, 2026

addedInput schema / properties / repo

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only projects built from this repository: `owner/repo` (case-insensitive; a full repository URL works too). Use it to see whether a repository is already linked and from which folders. `limit` applies after the filter.",
+  "title": "Repo"
+}

Changed5 schema fields changedSep 18, 2026

changedInput schema / properties / limit / description

Previous value: -"Сколько последних проектов вернуть. По умолчанию 30 — этого хватает почти всегда; поднимай, только если пользователь ищет старый сайт и в списке его нет."New value: +"How many of the most recent projects to return. The default of 30 is almost always enough; raise it (up to 100) only when the user is looking for an old site that is not in the list."

changedOutput schema / $defs / ProjectBrief / description

Previous value: -"Проект в списке — только то, по чему его узнают и на что жмут.\n\nПоля отобраны по весу в контексте, а не по полноте: MCP отдаёт результат\nДВАЖДЫ (текстом и структурой), поэтому каждое лишнее поле стоит двойной\nцены. На 66 проектах полная карточка давала 33 КБ — столько агент\nпотратил бы на один вопрос «какие у меня сайты».\n\n`id` не отдаём: остальные инструменты принимают слаг и резолвят его сами.\n`name` почти всегда совпадает со слагом, `framework` спрашивают редко."New value: +"A project in the list — only what identifies it and says where it is built from."

addedOutput schema / $defs / ProjectBrief / properties / branch

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

addedOutput schema / $defs / ProjectBrief / properties / repo

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

addedOutput schema / $defs / ProjectBrief / properties / root_directory

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

Changed1 schema field changedAug 3, 2026

addedInput schema / properties / limit / description

Added value: +"Сколько последних проектов вернуть. По умолчанию 30 — этого хватает почти всегда; поднимай, только если пользователь ищет старый сайт и в списке его нет."

AddedJul 27, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safe read behavior is covered. The description adds value by explaining the semantics of the returned fields (url, repo, branch, root_directory) and their null cases, as well as the context-flooding concern behind the default limit. This goes beyond the annotations without contradicting them.

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 compact and well-organized: a single-sentence purpose, a rationale for the default limit, and a separate paragraph for field semantics. It is front-loaded with the core function and avoids fluff, though it could be trimmed slightly without losing meaning.

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 that an output schema exists and annotations cover safety, the description fully covers the essential behavioral and field details. It explains default behavior, when to adjust the limit, and the meaning of null values, leaving no critical gaps for an agent to call this tool correctly.

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 coverage is 100%, so both parameters (repo and limit) are documented. The description adds extra guidance: for repo, it suggests using it to check repository linkage and folders; for limit, it explains when to raise it. This enhances the schema definitions 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 opens with 'The user's sites on Layero,' which clearly indicates a listing of the user's projects. It further clarifies the default limit and the fields returned, so an agent can infer it is a read-only list. It does not explicitly use a verb like 'list,' but the intent is unambiguous and distinct from any sibling tool.

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?

The description provides context on when to adjust the default limit ('raise it only when the user is looking for an old site'), and it explains the rationale for the 30-item default. However, it does not mention any alternative tools or explicitly state when to choose this tool over others, though no sibling appears to directly compete with it.

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

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

Need Help?