Skip to main content
Glama

Hatch

by com.viberooster

Check identity

whoami
Read-onlyIdempotent

Return the caller's current identity and tenant state. Never errors when unidentified — returns a pairing path instead. After poll_pairing completes, whoami with the same tenantId should show identified:true via server-side session binding. Returns sessionExpiresAt (~1h) and grantExpiresAt (~7d). If sessionExpired:true, call refresh_session with your stored refreshToken.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tenantIdNoOptional tenant to check or re-pair against.
sessionTokenNoOptional token from poll_pairing. Pass when whoami stays unidentified after a successful pair (connectors that cannot set Authorization headers).

TDQS

A5/5.0
Behavior5/5

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

While annotations already indicate readOnly and idempotent, the description adds substantial behavioral detail: never errors when unidentified, returns a pairing path, server-side session binding, sessionExpiresAt (~1h), grantExpiresAt (~7d), and sessionExpired handling. This is valuable beyond the 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 dense but well-structured, front-loading the purpose and then providing sequential, non-redundant behavioral notes. Every sentence contributes essential functionality, staying within a reasonable length.

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?

With no output schema, the description compensates by listing return fields (sessionExpiresAt, grantExpiresAt, sessionExpired) and explaining failure/edge behavior. It also references sibling tools and tie-in to poll_pairing and refresh_session, making it fully self-sufficient for an agent.

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

Parameters5/5

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

Input schema already covers both parameters (tenantId, sessionToken), and the description enriches them by explaining when to pass sessionToken (connectors that cannot set Authorization headers) and how tenantId relates to re-pairing. This adds meaning beyond schema descriptions.

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 'Return the caller's current identity and tenant state,' a specific verb+resource. It distinguishes itself from siblings like poll_pairing and refresh_session by referencing the pairing flow and session renewal, making its unique role clear.

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 concrete usage context: when to call after poll_pairing, how to handle unidentified states, and when to delegate to refresh_session on sessionExpired. This effectively guides selection among the sibling tools.

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