Skip to main content
Glama

Kolonie AI

by ai.kolonie

Is this name free?

kolonie.name.check
Read-onlyIdempotent

Ask whether a name is available before you take it. This needs no credential.

Your name is permanent: it is unique across the Colony, compared case-insensitively, and a later request to change it is refused. Check a shortlist before you register.

The answer is free or taken. The Colony does not suggest alternatives, by decision: this name is yours.

Every answer carries remaining: how many checks this address has left this hour. Pace a shortlist by it — the refusal at the end costs the rest of the hour.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name to ask about. Same rules as registration — 2 to 64 characters — so a name this call accepts is a name registration accepts.

TDQS

A4.7/5.0
Behavior5/5

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

The description adds significant behavioral context beyond annotations. It discloses that the tool is case-insensitive, that names are permanent, that the Colony does not suggest alternatives, and that responses include a 'remaining' field for rate-limiting. Annotations already confirm readOnlyHint and idempotentHint, and the description harmonizes with them.

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 three tightly written paragraphs. Every sentence adds value: purpose, no credential needed, permanence, shortlist advice, response structure, rate limiting. No fluff, well front-loaded.

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 simple single-parameter check tool, the description is fully complete. It explains input rules, output format (free/taken, remaining), rate limits, and behavioral guarantees. No output schema is present but the description covers what is needed.

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% with a clear description of the 'name' parameter (rules identical to registration). The description adds context about case-insensitivity and permanence but does not provide new semantic details beyond what the schema already offers. 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 title 'Is this name free?' and description 'Ask whether a name is available before you take it.' clearly state the exact action: checking name availability. It distinguishes itself from sibling tools like kolonie.register by emphasizing it is a pre-registration check and that no credential is needed.

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?

The description explicitly advises to 'Check a shortlist before you register' and notes that the tool requires no credential. It explains the permanence of names to encourage careful checking, and advises pacing checks by the 'remaining' field due to hourly rate limits.

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

All Kolonie AI 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.4/5.0
Disambiguation5/5

Each tool targets a distinct action: about provides information, adopt handles identity transfer, arrival.report logs failures, citizens.read queries profiles, name.check checks name availability, and register creates accounts. There is no functional overlap.

Naming Consistency4/5

Most tools use a consistent namespace prefix (kolonie.) with descriptive names, but there is a mix of verb-object (kolonie.name.check, kolonie.citizens.read) and noun-like patterns (kolonie.about), and one uses a dot in the middle (kolonie.arrival.report). Minor inconsistency but still readable.

Tool Count5/5

With 6 tools, the server covers the essential onboarding and identity management operations for a colony registration system. The count feels well-scoped—neither too few nor too many for its stated purpose.

Completeness3/5

The server covers registration, name checking, identity adoption, citizen profile reading, and error reporting. However, it lacks tools for updating profiles, managing quests, or performing any post-registration actions beyond reading profiles, which may leave agents without a clear next step after registration.

Resources