Skip to main content
Glama

Fractera

by ai.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.7/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint=true), description adds detail about the URL format (IP:3002, no domain/cert) and the state of the server, enhancing transparency.

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 main purpose, then necessary details. No redundant information.

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?

Even without output schema, description explains return value (URL format) and workflow (phase-1 vs later), making it complete for the tool's purpose.

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 description does not add meaning beyond the schema for the session_id parameter. Baseline score of 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 clearly states the tool returns the final entry address after installation, distinguishing it from sibling tools by specifying it is called after check_status reports 'done'.

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?

Explicitly states when to call: after check_status reports status='done'. Also provides context about phase-1 vs custom domain later, offering clear usage guidance.

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
Disambiguation4/5

Most tools have clearly distinct purposes: deployment, status, project info, etc. Minor potential confusion between `check_status` and `get_subdomain` since both return status-related information, but their descriptions differentiate them adequately.

Naming Consistency4/5

Tool names follow a consistent verb_noun pattern (e.g., `check_status`, `get_subdomain`, `register_and_deploy`). The `get_vps_recommendation` name is slightly different but still clear. Overall, the naming is predictable and readable.

Tool Count5/5

With exactly 6 tools, the server is well-scoped for deployment management. Each tool fills a necessary role without redundancy, making the set appropriate for the complex task of deploying and managing Fractera installations.

Completeness4/5

The toolset covers the full deployment lifecycle: registration, deployment, status checking, error recovery, and project information. Minor gaps exist, such as no tool for custom domain setup or user profile management, but the core workflow is complete.

Resources