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.

Провайдеры и подключения репозиториев

list_sources
Read-onlyIdempotent

Which git providers Layero supports and which of them the organization has connected (GitHub App installations and provider tokens).

Call before `import_repo` when you are not sure the provider is
connected. Connecting a provider token is done by the person in the
dashboard — never ask them to paste the token into the chat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationNoOrganization slug. Without it — the account's only organization, or the personal one; if there are several and none is personal, the tool lists the slugs.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountsYes
providersYes
connect_urlYes
next_actionYes
organizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / organization / description
      Previous value: -"Слаг организации. Без него — единственная организация аккаунта или личная; если их несколько и личной нет, инструмент перечислит слаги."New value: +"Organization slug. Without it — the account's only organization, or the personal one; if there are several and none is personal, the tool lists the slugs."
    • changedOutput schema / $defs / SourceAccountBrief / description
      Previous value: -"Откуда можно импортировать: установка GitHub App или токен провайдера."New value: +"Where a repository can be imported from: a GitHub App installation or a provider token."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds valuable behavioral context: that connecting tokens is done by a human in the dashboard, not via this tool, and that the tool is a prerequisite check. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences: purpose first, then when to use, then a critical behavioral note. No wasted words, information is front-loaded, and every sentence carries meaningful guidance. Very well structured.

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?

For a simple read-only listing tool with one optional parameter and an output schema, the description covers purpose, usage timing, and a security-relevant instruction. Nothing an agent needs to call it correctly is missing, especially with annotations covering safety and idempotency.

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

Parameters3/5

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

The single parameter 'organization' is fully described in the schema, including default behavior and ambiguity resolution. The description adds no extra parameter detail, so with 100% schema coverage the baseline of 3 is appropriate. The description's focus is on usage context rather than parameter semantics.

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 explicitly states the tool lists supported git providers and which are connected (GitHub App installations and provider tokens). It clearly identifies the resource and action, and distinguishes itself from siblings by referencing import_repo and the provider connection context.

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?

Provides explicit usage guidance: call before import_repo when unsure about provider connection. It also gives a critical behavioral instruction about never asking users to paste tokens, which prevents misuse. This clearly routes the agent to the right time and context.

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