Skip to main content
Glama

unulu

by ai.unulu

Get site state

unulu_get_state
Read-only

Returns the current state of a site including its name, bio, links, and URL. No authentication required. If expires_at is absent, the site has been claimed and is permanent. Accepts a site ID, a full URL (e.g. https://abc123.unu.lu), or a bare hostname (e.g. abc123.unu.lu).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idYesSite ID, full URL (e.g. https://abc123.unu.lu), or bare hostname (e.g. abc123.unu.lu)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bioNo
urlYes
nameYes
linksYes
site_idYes
skin_idNo
expires_atNo

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context: 'No authentication required' and the expires_at semantics for claimed vs. permanent sites, going beyond structured data.

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?

Two sentences, front-loaded with the core function, followed by essential details. Every sentence earns its place with no redundancy or filler.

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 the output schema exists, the description need not explain return values. It covers input flexibility, authentication, and the expires_at behavioral nuance, making it complete for a simple read tool.

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% and already describes the site_id formats. The description repeats these formats without adding additional semantic meaning beyond what the schema provides, so baseline 3 is appropriate.

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 states a specific verb ('Returns') and resource ('current state of a site'), listing key fields and input formats. It clearly distinguishes from siblings (create/update/check_handle) as a read-only retrieval tool.

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?

The description implies usage context: retrieving site state with flexible input forms and no auth. It doesn't explicitly name alternatives or exclusions, but the read vs. write distinction is clear from sibling names and the description.

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

All unulu 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

A4.6/5.0
Disambiguation5/5

Each tool has a distinct purpose with no overlap: check_handle verifies availability, create_site builds a new site, get_state retrieves current site data, and update_site modifies an existing site. The descriptions clearly differentiate their functions, preventing agent misselection.

Naming Consistency5/5

All tools follow a consistent 'unulu_verb_noun' pattern (e.g., unulu_check_handle, unulu_create_site). This uniformity makes the tool set predictable and easy for agents to understand and navigate.

Tool Count5/5

With 4 tools, this server is well-scoped for handling link-in-bio sites on unu.lu. It covers the essential lifecycle: checking availability, creating, reading, and updating sites, which is appropriate for its focused domain without being overly sparse or bloated.

Completeness4/5

The tool set provides strong coverage for the core site lifecycle (check, create, read, update), but lacks a delete tool for removing sites. This minor gap can be worked around by agents, as the domain is otherwise well-covered with no dead ends in typical workflows.

Resources