Skip to main content
Glama

Fractera

by io.github.Fractera

Get Workspace Address

get_subdomain
Read-only

Return the final entry address of the server once installation is complete. In phase-1 (IP-first) this is a plain-HTTP Admin URL of the form http://:3002 — the server has NO domain and NO HTTPS cert yet (attaching a custom domain with HTTPS is an optional later step the user does inside Admin -> Personal Domain). Call this once after check_status reports status="done".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesThe session_id used during installation.

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already mark it as read-only and non-destructive. The description adds context about the phase-1 address format (HTTP, IP, no domain/HTTPS), which goes beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is well-structured with purpose, format, and usage instructions in a few sentences. Slightly verbose but each sentence adds value.

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 simple single parameter and no output schema, the description fully covers what the tool returns and when to use it, including edge cases like phase-1 constraints.

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%; the description does not add meaning beyond the schema's description of the session_id parameter. Baseline score applies.

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 clearly states that the tool returns the final entry address of the server after installation, specifying the form in phase-1 and distinguishing it from siblings like check_status and get_project_info.

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?

Explicitly says to call this after check_status reports 'done', providing clear usage context. Does not explicitly mention when not to use, but the instruction is sufficient.

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

All Fractera 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 serves a distinct, non-overlapping purpose: status checking, project info, subdomain retrieval, VPS recommendation, deployment registration, and retry. No two tools could be confused for the same task.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_status, get_project_info, register_and_deploy). The naming is predictable and clear.

Tool Count5/5

Six tools is appropriate for the server's scope—deploying and managing a single Fractera server. Each tool is essential and covers the core workflow without unnecessary bloat.

Completeness4/5

The tool set covers the main deployment lifecycle: recommendation, deploy, status check, subdomain retrieval, and retry. Minor gaps exist (e.g., no tool to update deployment configuration or list historical deployments), but the core user journey is complete.

Resources