Layero

Скачать исходники деплоя

download_source

Read-only

A short download link to a ZIP of what a build was made from.

For an upload (`npx layero@latest deploy`) the ZIP holds the uploaded
sources; for a site published with `publish_site` — the published files.
`.env*` files are left out. Needs a member who can deploy (editor role).
The link works for 5 minutes: hand it to the person, do not fetch it
yourself unless they asked you to work with the files.

A build made from a repository has no stored sources — you get the commit
link instead. Old uploads may be gone: the platform keeps sources 7 days,
and the live build while it is live.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "download_source"
  }
}

Input Schema

Name	Required	Description	Default
`deploy`	No	id of the build (from list_deploys). Without it — the build served on the project address.
`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
`url`	No
`project`	Yes
`filename`	No
`deploy_id`	Yes
`commit_url`	No
`expires_in`	No
`next_action`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond readOnlyHint/openWorldHint the description discloses the important behaviours: the link expires in 5 minutes, an editor-role member is required, `.env*` files are stripped, sources are retained 7 days plus the live build's lifetime, and repository builds return a commit link instead of a ZIP. Those are exactly the facts an agent cannot get from the 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?

Front-loaded with the one-line answer, then progressively rarer caveats. Five sentences is a bit long but each carries a distinct operational fact; no filler or repetition.

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 two-parameter, non-mutating lookup with full schema coverage and an output schema, everything an agent needs is present: permission gate, link lifetime, content exclusions, retention window, and the failure mode for repo-based builds.

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?

Schema coverage is 100%, so both `project` and `deploy` are already fully documented, including the slug-vs-host caveat and the list_deploys provenance of the build id. The description adds no parameter-level meaning beyond that, which is the baseline 3 case.

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 a concrete verb+resource: a download link to a ZIP of a build's sources, and it itemises what the ZIP contains for uploads vs. published sites vs. repository builds. That distinguishes it from data-returning siblings like list_sources. It does not explicitly name the sibling to prefer when you only want source metadata, so a 4 rather than 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 clear when-to-use framing (hand the link to the person; do not fetch it yourself unless asked) and when-not conditions (repository builds have no stored sources — you get a commit link; uploads older than 7 days are gone). It stops short of naming an alternative tool such as list_sources for the metadata-only case.

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.