Skip to main content
Glama
Sign In

Xenition

by com.xenition.api
OverviewDiscussionsAdmin

Open the app builder

open_app_builder
Read-only

Use this when the user wants to open Xenition's no-code app builder themselves, pre-filled with their idea, to shape the app by hand. This builds nothing — it returns a link that opens the builder. To have the app built for them from the conversation, use build_app instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "idea": "<idea>"
    },
    "name": "open_app_builder"
  }
}

Input Schema

NameRequiredDescriptionDefault
ideaYesa clear description of the app to build, distilled from the conversation (e.g. 'a task tracker with projects, due dates, and team assignments')
nameNoa short app name (e.g. 'Task Tracker')
mobileNotrue to also target mobile (web + mobile), otherwise web only

Output Schema

NameRequiredDescriptionDefault
ideaYes
nameNo
mobileYes
openUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/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, so safety is covered. The description adds real value beyond that: it discloses that no build occurs and that the return value is a link, which prevents the agent from assuming this produces an app. It stops short of describing the link's lifetime or any auth/session requirements.

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?

Three short sentences, front-loaded with the usage trigger followed immediately by the negative capability statement and the routing alternative. No 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?

An output schema exists, so return mechanics need not be spelled out, and the description still notes the link return. All parameters are schema-documented and the sibling disambiguation covers the main selection risk for a 60-plus tool workspace.

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 description coverage is 100% and each of the three parameters is documented in the schema with examples. The description adds nothing parameter-level (e.g. it does not explain how 'idea' should be distilled or when 'mobile' matters), so the baseline 3 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?

States a specific verb (open) and resource (Xenition's no-code app builder) with the qualifier 'pre-filled with their idea, to shape the app by hand.' It also explicitly disclaims what it does not do ('This builds nothing') and names the sibling it differs from (build_app).

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?

Gives an explicit trigger ('when the user wants to open ... themselves') and an explicit alternative with its own condition ('To have the app built for them from the conversation, use build_app instead'). The when/when-not decision is fully resolved.

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

All Xenition toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources