AbleSign MCP

create_web_app

Create a web app from a URL or raw HTML for digital signage. Specify title and description to manage content on AbleSign screens.

Instructions

Create a web app from either a URL or raw HTML.

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": {
      "title": "<title>"
    },
    "name": "create_web_app"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No
`html`	No
`title`	Yes
`description`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description must disclose side effects, permissions, or persistence, but it only states the basic function. It does not explain what happens upon creation (e.g., is it saved, what is the response) or any authorization requirements. This is insufficient for an AI agent.

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?

The description is a single efficient sentence that communicates the core action immediately. It avoids redundant information, earning its place. However, it could be slightly expanded to include key parameter details without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite an output schema existing, the description does not provide essential context such as the mutual exclusivity of url and html, the required title, or any prerequisites like workspace membership. The tool has 4 parameters with 0% schema coverage, so the description must compensate but does not fully address these gaps.

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?

The description adds meaning by indicating that 'url' and 'html' are alternative sources, which is not clear from the schema alone. However, it fails to mention the required 'title' parameter or explain the 'description' parameter. With 0% schema coverage, this partial explanation is helpful but incomplete.

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 action ('Create a web app') and the two source options ('from either a URL or raw HTML'). It distinguishes this creation tool from its siblings like 'update_web_app' and 'delete_web_app' by focusing on creation. The purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus other tools like 'update_web_app' or 'list_web_apps'. There is no mention of prerequisites, such as needing a workspace, or that only one of url/html should be provided. The description lacks decision-making context.

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

Deploy Server