list_structuresReturn the catalogue of landing structures Layero ships with.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint; the description adds minimal context that the catalogue is pre-shipped by Layero ('ships with'), but doesn't detail structure shape or output behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with no redundant words, placing the verb and object upfront. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With zero parameters, an existing output schema (not shown but present), and read-only/idempotent annotations, the description is sufficient for a simple catalogue listing; nothing critical is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the schema fully covers parameter semantics; the description adds nothing needed for this dimension.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the explicit verb 'Return' and specifies the resource as 'catalogue of landing structures Layero ships with,' distinguishing it from sibling list tools like list_design_systems and list_domains.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives is provided; usage is implied by the name and simple read-only nature, but there are no exclusions or alternative references.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action. The deploy lifecycle is cleanly separated into cancel, retry, rollback, diagnose, logs, list, and status, while the site_* tools each answer a different question. Even the two compose_landing tools are explicitly differentiated for model vs. internal use.
Tool names mix verb-first patterns (check_domain, list_deploys, connect_analytics) with noun-first patterns (site_issues, deploy_logs, env_vars), and some are bare verbs (rollback, whoami). The naming is descriptive and readable, but not consistent enough to predict the style for a new tool.
27 tools exceeds the typical well-scoped range and pushes into 'too many' territory. While the server covers a broad platform scope, many tools are highly specialized (check_copy, site_screenshot), and an agent may be overwhelmed by the sheer number of choices. Consolidation could reduce the load.
The core lifecycle is solid: compose, publish, monitor, diagnose, and rollback, with supporting tools for domains, analytics, performance, and content inspection. However, there are no delete/remove operations for projects, domains, or integrations, and integration management is limited to adding. These are minor gaps that agents can work around, but they are notable for a full platform.