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.

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

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

TableJSON Schema
NameRequiredDescriptionDefault
waitNoWait for the measurement result (tens of seconds) or return at once. `false` — when the user needs the run started, not its result.
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
deltaYes
scoreYes
messageYes
projectYes
timingsYes
verdictYes
next_actionYes
previous_scoreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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."
  2. Changed2 schema fields changed
    • addedInput schema / properties / project / description
      Added value: +"Проект: слаг (`my-site`) или id. Слаг — то, что видно в адресе сайта; если пользователь назвал сайт словами, возьми слаг из `my_projects`."
    • addedInput schema / properties / wait / description
      Added value: +"Дождаться результата замера (десятки секунд) или вернуться сразу. `false` — когда пользователю нужен не результат, а сам факт запуска."
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that a run takes tens of seconds, wait=true blocks, a parallel measurement occupies the queue, and the score behaves differently from raw timings. This is substantial, useful behavioral context that the annotations alone do not provide.

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?

Three short paragraphs, no filler. The purpose is front-loaded, and every sentence earns its place: the statistical caveat is essential for correct interpretation, and the queue warning is actionable guidance.

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 output schema exists, return-value details are not required. The description covers how to invoke, how long the call takes, wait behavior, concurrency constraints, and how to judge the verdict. An agent has enough to call it 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% and the schema already describes both parameters. The description adds value by explaining the operational consequence of wait=true ('do not start a second measurement in parallel — it will occupy the queue'), which enriches the wait parameter semantics even though the schema handles the basics.

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 first sentence states a specific verb plus resource: 'Measure a site's speed and say whether it got worse after a deploy.' This clearly distinguishes it from siblings like site_status or site_analytics by naming the exact purpose and the regression verdict.

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?

The description gives clear context for when to use the tool (after a deploy), explains how to interpret results (3+ point difference is meaningful, smaller is noise), and warns against parallel runs. It does not name alternative sibling tools explicitly, so it falls just short of the top score.

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