Publishes a specified Tealfabric webapp version to make it live, enabling you to release the intended app version to users.
Publish a Tealfabric webapp version (make that version live).
| Name | Required | Description | Default |
|---|---|---|---|
| version | Yes | Version number to publish (required) | |
| webapp_id | Yes | Webapp UUID |
Changes observed during successful MCP inspections.
v0.2.0Input schema / additionalPropertiesRemoved value: -falseInput schema / properties / versionAdded value: +{
+ "description": "Version number to publish (required)",
+ "exclusiveMinimum": 0,
+ "maximum": 9007199254740991,
+ "type": "integer"
+}Input schema / requiredPrevious value: -[
- "webapp_id"
-]New value: +[
+ "webapp_id",
+ "version"
+]v0.1.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral-disclosure burden. It states the publish effect ('make that version live'), but does not disclose reversibility, permission requirements, impact on an already-live version, or other operational traits of this mutating action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no wasted words. It states the action and its practical effect immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The purpose and both parameters are clear, and no output schema exists to require return-value explanation. However, for a mutating publish operation with no annotations, the description should say more about operational consequences and prerequisites.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and both required parameters (webapp_id, version) are documented in the schema. The description adds no parameter-level semantics beyond the schema, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Publish') and resource ('Tealfabric webapp version') and clarifies the effect with '(make that version live).' This distinguishes it reasonably from version-creation and update siblings, though it does not explicitly name alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool makes an existing version live, but gives no explicit when-to-use guidance, prerequisites, or comparison to siblings such as tealfabric_create_webapp_version, tealfabric_update_webapp, or tealfabric_unpublish_webapp.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.