Skip to main content
Glama

Hatch

by com.viberooster

Rename or change tier

convert
DestructiveIdempotent

Atomically rename a roost's URL and/or change its tier. Pass tenantId plus at least one of newPreferredSlug (rename), newTier (e.g. free → forever), or galleryListed (opt in/out of the Barnyard carousel on viberooster.com). Do NOT call hatch again to upgrade — that creates a second site with a new id.

Forever roosts are hidden from the carousel by default; pass galleryListed: true when promoting to forever to feature the site publicly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
newTierNoNew tier. Clears `expiresAt` when promoting to `forever`.
tenantIdYes
sessionTokenNoOptional paired session token from poll_pairing (when Authorization headers are unavailable).
galleryListedNoOpt in (`true`) or out (`false`) of the public Barnyard carousel. Forever tier requires `true` to appear; free tier is listed unless set to `false`.
newPreferredSlugNoNew hostname label. The old slug is released atomically.

TDQS

A4.9/5.0
Behavior5/5

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

Discloses atomicity ('Atomically'), that the old slug is released, that forever roosts are hidden from the carousel by default, and that 'galleryListed: true' is required to feature publicly. These details go beyond the destructiveHint/idempotentHint annotations and clarify real side effects. No contradiction with annotations.

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?

The description is front-loaded with the primary action and is compact. Every sentence adds essential information: the atomic rename/tier change, the requirement to pass tenantId plus one field, the explicit warning about hatch, and the carousel visibility caveat. No filler or repetition of schema details.

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 no output schema and 5 parameters, the description covers all necessary invocation context: the required parameter, which combinations are valid, a critical sibling-tool pitfall, and behavioral effects (gallery visibility, slug release). It is sufficiently complete for correct selection and invocation without additional external knowledge.

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 80%, so the schema already documents most parameters. The description adds meaningful semantics by grouping parameters ('Pass tenantId plus at least one of...'), explaining the meaning of newPreferredSlug as 'rename', giving a concrete tier example ('free' → 'forever'), and clarifying galleryListed behavior not fully captured in the schema.

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 opens with a specific verb+resource: 'Atomically rename a roost's URL and/or change its tier.' It clearly distinguishes from the 'hatch' sibling by warning that calling 'hatch' again creates a second site. The scope (URL rename, tier change, gallery listing) is fully covered.

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 when-to-use guidance: pass 'tenantId' plus at least one of the three mutable fields. Explicitly names an alternative and warns against it: 'Do NOT call hatch again to upgrade — that creates a second site with a new id.' Also gives context for gallery listing behavior when promoting to forever.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Hatch toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation3/5

Core actions like hatch, convert, upload, and lookup are generally distinct, but the polling family (poll_approval, poll_decision, poll_pairing) is easy to confuse, and await_decision misleadingly sounds like a wait operation rather than the creation of a review. Descriptions clarify boundaries, but the names alone leave room for misselection.

Naming Consistency3/5

Most tools use an imperative verb style, but the pattern is inconsistent: some are bare verbs (hatch, convert, deploy, list, lookup, share, upload), some are verb_noun (poll_decision, refresh_session, get_pairing_code), and auth is a bare noun. The names are readable but do not follow one predictable convention.

Tool Count3/5

16 tools sits at the heavy end of the comfortable range, inflated by three polling tools plus pairing/session management that are only tangentially related to the core task of creating and updating roosts. Each tool has a purpose, but the surface feels larger than the core domain requires.

Completeness3/5

The set covers create, read/list, update via convert/upload/deploy, sharing, and auth, but there is no delete/destroy or teardown tool, and custom domain/state management is only passively visible through lookup. Agents can complete common workflows but will hit dead ends on teardown or lifecycle management.

Resources