Skip to main content
Glama

recipebooq

by com.recipebooq
OverviewDiscussionsAdmin

Add a screen to an app

add_screen
Read-onlyIdempotent

Needs a subscription. Adds one screen designed in the Architect to a project. With the project's .opointo/files.json it returns the screen file, the route that mounts it and the one line to register it, and never rewrites existing files. Without it, a self-contained screen file for any Expo app.

Input Schema

NameRequiredDescriptionDefault
tabNonest it in this tab's stack; omit to place it where the design does
appIdYesthe share code from "Send app to agent"
screenNothe new screen's name in that design
manifestNothe parsed .opointo/files.json
componentNameNoonly to add a second copy of a screen; omit for the export's name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / componentName / description
      Previous value: -"e.g. \"InvoiceScreen\""New value: +"only to add a second copy of a screen; omit for the export's name"
    • changedInput schema / properties / tab / description
      Previous value: -"nest it in this tab's stack; omit for the root, which covers the tab bar"New value: +"nest it in this tab's stack; omit to place it where the design does"
  2. Changed7 schema fields changed
    • addedInput schema / properties / appId
      Added value: +{
+  "description": "the share code from \"Send app to agent\"",
+  "type": "string"
+}
    • changedInput schema / properties / componentName / description
      Previous value: -"React component name, e.g. \"InvoiceDetail\". Defaults to GeneratedScreen."New value: +"e.g. \"InvoiceScreen\""
    • removedInput schema / properties / compositionId
      Removed value: -{
-  "description": "share code for the new screen, from the App Builder",
-  "type": "string"
-}
    • changedInput schema / properties / manifest / description
      Previous value: -"the parsed .opointo/files.json from the project root"New value: +"the parsed .opointo/files.json"
    • addedInput schema / properties / screen
      Added value: +{
+  "description": "the new screen's name in that design",
+  "type": "string"
+}
    • changedInput schema / properties / tab / description
      Previous value: -"nest it in this tab's stack so the tab bar stays visible. Omit to put it at the root, where it covers the tab bar (right for a modal)."New value: +"nest it in this tab's stack; omit for the root, which covers the tab bar"
    • changedInput schema / required
      Previous value: -[
-  "compositionId",
-  "manifest"
-]New value: +[
+  "appId"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / manifest / description
      Previous value: -"the parsed .recipebooq/files.json from the project root"New value: +"the parsed .opointo/files.json from the project root"
  4. Changed1 schema field changed
    • changedInput schema / properties / compositionId / description
      Previous value: -"share code for the new screen, from the composer"New value: +"share code for the new screen, from the App Builder"
  5. Added

TDQS

A3.7/5.0
Behavior4/5

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

Adds real context beyond the annotations: subscription gating, the guarantee that existing files are never rewritten, and mode-dependent outputs (screen file + mounting route + registration line vs. a standalone file). These details clarify that 'add' produces artifacts rather than mutating state, consistent with readOnlyHint=true.

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?

Dense and front-loaded with the subscription prerequisite first. The telegraphic, clause-fragmented style ('With the project's... Without it...') is efficient but slightly disjointed to parse.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and does explain the two possible outputs and the no-rewrite guarantee. It stops short of spelling out the route/registration payload structure, but an agent has enough to call it correctly.

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%, so the schema already explains appId, screen, manifest, tab, and componentName. The description adds mode context around 'manifest' but no per-parameter syntax or format detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: adds one Architect-designed screen to a project, and distinguishes the two output modes (manifest-aware vs. self-contained Expo file). However, it never differentiates from sibling tools like propose_screen or emit_app, which could plausibly be confused with this operation.

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?

Gives a prerequisite ('Needs a subscription') and describes the two execution contexts (with vs. without the project's .opointo/files.json), but never says when to choose this over propose_screen or emit_app. Usage is implied rather than prescribed.

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

All recipebooq toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources