Skip to main content
Glama
Sign In

Forge Engine

by app.forgeengine
OverviewDiscussionsAdmin

design_ui_from_systems

Read-only

Recipe to design the UI from Systems (user request only): steps + batch id — confirm canvas aspect, then screens + PLACED elements + edges in one batch.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "design_ui_from_systems"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / project_id / description
      Removed value: -"Project id (from list_projects) to act on; omit = the connector URL's project."
  2. First observed

TDQS

C2.7/5.0
Behavior1/5

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

The description contradicts the readOnlyHint annotation by describing the creation/placement of screens, elements, and edges, which are write operations. Additionally, it provides no details about side effects, permissions, or return behavior. This is a serious inconsistency.

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 brief and front-loaded with the purpose, but the 'steps + batch id' phrasing is cryptic. It is not overly verbose and earns a 4 for efficiency, though it could be clearer.

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

Completeness1/5

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

The tool appears to be a complex batch orchestration, yet the description omits critical information such as how the batch id works, what the steps entail, what output to expect, and how project_id factors in. Without an output schema and with the annotation contradiction, the description is wholly inadequate for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not explain the project_id parameter at all, and the schema has 0% description coverage. The mention of 'batch id' is ambiguous and may not correspond to project_id. The agent is left without meaningful parameter semantics.

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 is a 'Recipe to design the UI from Systems' and describes a batch process of confirming canvas aspect and creating screens, placed elements, and edges. This distinctively separates it from individual proposal tools like propose_screen or propose_element. The 'user request only' qualifier adds scope.

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

Usage Guidelines3/5

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

The description implies usage when a user requests a batch UI design from systems, but does not explicitly name alternatives or state when not to use it. It mentions 'batch' and 'user request only' but lacks exclusionary guidance; the contrast with sibling proposal tools is implicit rather than explicit.

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

All Forge Engine 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