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.

Замерить скорость сайта

check_performance

Read-only

Measure a site's speed and say whether it got worse after a deploy.

The verdict comes FROM THE SCORE, not from timings: repeated runs of the
same deploy vary by at most one point, while LCP and TTFB on identical
code swing by 37-40%. A difference of 3 points or more is meaningful;
anything smaller is measurement noise, and calling that a regression is
inventing a problem.

A run takes tens of seconds. With `wait=true` the tool waits for you; do
not start a second measurement in parallel — it will occupy the queue
and add nothing.

Input Schema

Name	Required	Description	Default
`path`	No	Page path on the production branch, e.g. `/pricing`. Default — the home page.	/
`wait`	No	Wait for the measurement result (tens of seconds) or return at once. `false` — when the user needs the run started, not its result.
`device`	No	`mobile` — throttled phone like most visitors; `desktop` — fast network.	desktop
`project`	Yes	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.

Output Schema

Name	Required	Description	Default
`brief`	No
`delta`	Yes
`score`	Yes
`message`	Yes
`project`	Yes
`timings`	Yes
`verdict`	Yes
`next_action`	Yes
`previous_score`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 1, 2026

addedInput schema / properties / device

Added value: +{
+  "default": "desktop",
+  "description": "`mobile` — throttled phone like most visitors; `desktop` — fast network.",
+  "enum": [
+    "desktop",
+    "mobile"
+  ],
+  "title": "Device",
+  "type": "string"
+}

addedInput schema / properties / path

Added value: +{
+  "default": "/",
+  "description": "Page path on the production branch, e.g. `/pricing`. Default — the home page.",
+  "title": "Path",
+  "type": "string"
+}

addedOutput schema / properties / brief

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

Changed2 schema fields changedSep 18, 2026

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."

changedInput schema / properties / wait / description

Previous value: -"Дождаться результата замера (десятки секунд) или вернуться сразу. `false` — когда пользователю нужен не результат, а сам факт запуска."New value: +"Wait for the measurement result (tens of seconds) or return at once. `false` — when the user needs the run started, not its result."

Changed2 schema fields changedAug 3, 2026

addedInput schema / properties / project / description

Added value: +"Проект: слаг (`my-site`) или id. Слаг — то, что видно в адресе сайта; если пользователь назвал сайт словами, возьми слаг из `my_projects`."

addedInput schema / properties / wait / description

Added value: +"Дождаться результата замера (десятки секунд) или вернуться сразу. `false` — когда пользователю нужен не результат, а сам факт запуска."

AddedJul 27, 2026

TDQS

A4.3/5.0

Behavior5/5

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

With readOnlyHint already declaring safety, the description still adds substantial behavior: a run takes tens of seconds, results are queued and concurrent runs are wasteful, and the verdict is derived from a score rather than raw timings because LCP/TTFB swing 37-40% on identical code. That is exactly the context an agent cannot get from annotations or schema.

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?

Well front-loaded: the purpose is in sentence one, then the interpretation rule, then the operational caveat. The variance statistics earn their space because they prevent false regression calls, though the capitalized emphasis and repetition of "measurement noise" cost a little tightness.

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?

An output schema exists, so return values need not be described. Combined with full schema coverage and readOnlyHint, the description supplies everything else an agent needs to call it correctly: cost in time, queue constraint, and how to interpret the verdict.

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 baseline is 3; the description adds real meaning on top by explaining the score-vs-timing interpretation and by tying `wait` to the no-parallel-run rule and the "started, not its result" case. It still doesn't discuss `device` or `path` semantics in prose, leaving those entirely to the schema.

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?

States a specific verb+resource ("measure a site's speed") plus the comparative intent ("say whether it got worse after a deploy"), which is far more than the title alone. It does not explicitly contrast itself with adjacent-looking siblings such as site_status or check_rules, so it stops short of a 5.

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

Usage Guidelines4/5

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

Gives concrete usage thresholds (3+ point difference is meaningful, smaller is noise) and an operational constraint (don't run a second measurement in parallel because it occupies the queue). It also scopes `wait=false` to "when the user needs the run started, not its result." No sibling alternatives are named, so no exclusion guidance.

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

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?